From MAILER-DAEMON Thu May 01 17:19:14 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19BLS7-0005YT-00
	for mharc-bug-commoncpp@gnu.org; Thu, 01 May 2003 17:18:51 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19BLRF-0005MA-00
	for bug-commoncpp@gnu.org; Thu, 01 May 2003 17:17:57 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19BLQp-0004Wc-00
	for bug-commoncpp@gnu.org; Thu, 01 May 2003 17:17:33 -0400
Received: from gnuftp.gnu.org ([199.232.41.6])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19BLQX-00044C-00
	for bug-commoncpp@gnu.org; Thu, 01 May 2003 17:17:13 -0400
Received: from thumbler.kulnet.kuleuven.ac.be ([134.58.240.45])
	by gnuftp.gnu.org with esmtp (Exim 4.10.13)
	id 19BLQW-00089k-00
	for bug-commoncpp@gnu.org; Thu, 01 May 2003 17:17:12 -0400
Received: from localhost (localhost [127.0.0.1])
	by thumbler.kulnet.kuleuven.ac.be (Postfix) with ESMTP
	id C55CB137830; Thu,  1 May 2003 23:16:12 +0200 (CEST)
Received: from crassus.kulnet.kuleuven.ac.be (crassus.kulnet.kuleuven.ac.be
	[134.58.240.63])
	by thumbler.kulnet.kuleuven.ac.be (Postfix) with ESMTP
	id 5F8A613768C; Thu,  1 May 2003 23:16:12 +0200 (CEST)
Received: from 192.168.159.128 (10-67-120-25.kotnet.org [10.67.120.25])
	by crassus.kulnet.kuleuven.ac.be (Postfix) with ESMTP
	id 322E113EC08; Thu,  1 May 2003 23:16:12 +0200 (CEST)
From: Dimitar Dimitrov <dimitar@yucom.be>
To: "klaus triendl" <triendl.kj@aon.at>
Date: Thu, 1 May 2003 23:16:11 +0200
User-Agent: KMail/1.5.1
References: <MNENKPHMOOKIHGCMGMEBGEBACDAA.triendl.kj@aon.at>
In-Reply-To: <MNENKPHMOOKIHGCMGMEBGEBACDAA.triendl.kj@aon.at>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="windows-1251"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200305012316.11674.dimitar@yucom.be>
X-Virus-Scanned: by KULeuven Antivirus Cluster
cc: bug-commoncpp@gnu.org
Subject: Re: change of socketport constructor
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 01 May 2003 21:18:49 -0000

Hi Klaus,

I still see some problems with the patch you sent. May be I miss something
but here is what I think:

1. The attach() method of SocketPort being protected forces the derived class 
to call it in its own constructor (there are other variants but this is most 
probably the way it's going be used).
Now think about a situation when there is one level more in the class 
hierarchy. If there is a class derived form the class that is already derived 
from SocketPort we end up with the initial problem - the service thread is 
running before the object is fully constructed (the object is attached to the 
service in the class immediately derived from SocketPort!!!). I don't see a 
good way to clean this. May be separating creation of the SocketPort from 
attaching it to the service. That means making attach public and going for 
two-step process - create then attach. The problem here is that this approach 
will most probably break some existing code.
Any opinions...??

2. About expired() method. The problems I see here is that some compilers 
depending on the warning level will not complain if a method does not return 
a value when it is supposed to. That means if there is some code that doesn't 
return anything because of the old signature of expired() will still compile 
without problems if the warning level is low. I don't know who compiles with 
switched off warnings so may this is not that relevant anyway...

Regards,
Dimitar




From MAILER-DAEMON Thu May 01 18:24:50 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19BMTK-0000q5-00
	for mharc-bug-commoncpp@gnu.org; Thu, 01 May 2003 18:24:10 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19BMSG-00080J-00
	for bug-commoncpp@gnu.org; Thu, 01 May 2003 18:23:04 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19BMS7-0007ek-00
	for bug-commoncpp@gnu.org; Thu, 01 May 2003 18:22:57 -0400
Received: from m309p008.adsl.highway.telekom.at ([62.47.206.136]
	helo=triendl.kj)	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 19BMRp-0007ES-00
	for bug-commoncpp@gnu.org; Thu, 01 May 2003 18:22:37 -0400
Received: (qmail 9666 invoked from network); 1 May 2003 22:22:24 -0000
Received: from unknown (HELO triendl.kj) (127.0.0.1)
  by loopback with SMTP; 1 May 2003 22:22:24 -0000
Date: Fri, 2 May 2003 00:22:24 +0200
From: triendl klaus <triendl.kj@aon.at>
To: Dimitar Dimitrov <dimitar@yucom.be>
Message-Id: <20030502002224.6b7b6a4e.triendl.kj@aon.at>
In-Reply-To: <200305012316.11674.dimitar@yucom.be>
References: <MNENKPHMOOKIHGCMGMEBGEBACDAA.triendl.kj@aon.at>
	<200305012316.11674.dimitar@yucom.be>
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i386-debian-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
cc: bug-commoncpp@gnu.org
Subject: Re: change of socketport constructor
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 01 May 2003 22:24:08 -0000

On Thu, 1 May 2003 23:16:11 +0200
Dimitar Dimitrov <dimitar@yucom.be> wrote:

> 1. The attach() method of SocketPort being protected forces the derived class 
> to call it in its own constructor (there are other variants but this is most 
> probably the way it's going be used).
> Now think about a situation when there is one level more in the class 
> hierarchy. If there is a class derived form the class that is already derived 
> from SocketPort we end up with the initial problem - the service thread is 
> running before the object is fully constructed (the object is attached to the 
> service in the class immediately derived from SocketPort!!!). I don't see a 
> good way to clean this. May be separating creation of the SocketPort from 
> attaching it to the service. That means making attach public and going for 
> two-step process - create then attach. The problem here is that this approach 
> will most probably break some existing code.

yes, you are right. i also thought about this point (the fact that attach() is protected is not my idea); one solution is to let the programmer deriving his own class somewhere down the hierarchy from SocketPort attach his class to the SocketService.

the other solution is that the server (which creates the socketport) attaches the socket; as the server also takes care of the service(s) (e.g. it creates the service or chooses which one to take if more are running) this would be a clean solution i think.

about breaking the code: i wonder whether someone already ran successfully the code because i had always the problem with the virtual function tables.
so, it didn't work reliably or me at all and i don't suppose that it does for others. therefore breaking the code shouldn't be an issue (my opinion)


> 2. About expired() method. The problems I see here is that some compilers 
> depending on the warning level will not complain if a method does not return 
> a value when it is supposed to. That means if there is some code that doesn't 
> return anything because of the old signature of expired() will still compile 
> without problems if the warning level is low. I don't know who compiles with 
> switched off warnings so may this is not that relevant anyway...

what happens if no value is returned?
is this possible at all? because expired() is virtual, g++-3.3 complains about conflicting return types if void expired() is defined in a derived class; i don't know about other compilers.


-- 
klaus triendl



From MAILER-DAEMON Fri May 02 05:14:50 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19BWd0-0005si-00
	for mharc-bug-commoncpp@gnu.org; Fri, 02 May 2003 05:14:50 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19BWcx-0005oa-00
	for bug-commoncpp@gnu.org; Fri, 02 May 2003 05:14:47 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19BWcw-0005mA-00
	for bug-commoncpp@gnu.org; Fri, 02 May 2003 05:14:46 -0400
Received: from nibbel.kulnet.kuleuven.ac.be ([134.58.240.41])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19BWby-0004Va-00
	for bug-commoncpp@gnu.org; Fri, 02 May 2003 05:13:46 -0400
Received: from localhost (localhost [127.0.0.1])
	by nibbel.kulnet.kuleuven.ac.be (Postfix) with ESMTP
	id 1D9324B6E4; Fri,  2 May 2003 11:13:45 +0200 (CEST)
Received: from crassus.kulnet.kuleuven.ac.be (crassus.kulnet.kuleuven.ac.be
	[134.58.240.63])	by nibbel.kulnet.kuleuven.ac.be (Postfix) with ESMTP
	id A8D714B6DF; Fri,  2 May 2003 11:13:44 +0200 (CEST)
Received: from 192.168.159.128 (10-67-120-25.kotnet.org [10.67.120.25])
	by crassus.kulnet.kuleuven.ac.be (Postfix) with ESMTP
	id 73AC413EC04; Fri,  2 May 2003 11:13:44 +0200 (CEST)
From: Dimitar Dimitrov <dimitar@yucom.be>
To: bug-commoncpp@gnu.org
Date: Fri, 2 May 2003 13:06:39 +0200
User-Agent: KMail/1.5.1
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200305021306.39374.dimitar@yucom.be>
X-Virus-Scanned: by KULeuven Antivirus Cluster
cc: triendl klaus <triendl.kj@aon.at>
Subject: Problem in ~Thread()
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 02 May 2003 09:14:48 -0000

Hi,

I think this is a bug in the Thread class and more precisely in ~Thread(). 

The problem is that Thread::terminate() deletes and sets Thread::priv to NULL. 
If the destructor of Thread is called afterwards it tries to access 
priv->_msgbuf, whithout checking whether priv == NULL, which results in a 
segmentation fault.

This is exactly what happens in SocketService destructor. It calls terminate ( 
that is Thread::terminate() ) and then ~Thread() is called.

Regards,
Dimitar





From MAILER-DAEMON Fri May 02 06:34:59 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19BXsW-0006Co-00
	for mharc-bug-commoncpp@gnu.org; Fri, 02 May 2003 06:34:56 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19BXqp-0004CU-00
	for bug-commoncpp@gnu.org; Fri, 02 May 2003 06:33:11 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19BXqi-00045q-00
	for bug-commoncpp@gnu.org; Fri, 02 May 2003 06:33:05 -0400
Received: from e-tel.pl ([80.244.136.158] helo=nit.pl)
	by monty-python.gnu.org with smtp (Exim 4.10.13)
	id 19BXnQ-0002qq-00
	for bug-commoncpp@gnu.org; Fri, 02 May 2003 06:29:40 -0400
Received: (MGT-SMTPD 6466 invoked by uid 89); 2 May 2003 12:27:23 -0000
Received: from 80.244.136.130.unregistered.ptc.pl (HELO nit.pl)
	(teku@nit.pl@80.244.136.130)
	by nit.pl with (MGT-SMTPD) SMTP; 2 May 2003 12:27:23 -0000
Message-ID: <3EB2484A.2030104@nit.pl>
Date: Fri, 02 May 2003 12:28:26 +0200
From: Jakub Zawierucha <Jakub.Zawierucha@nit.pl>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; PL;
	rv:1.3b) Gecko/20030210
X-Accept-Language: pl, en-us, en
MIME-Version: 1.0
To: bug-commoncpp@gnu.org
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-MGTAntiSpam-Rating: nit.pl 1.0 0/1000/N
Subject: Undefined reference problem on 1.0.9
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 02 May 2003 10:34:53 -0000

Hi there... this is my first battle with CommonC++ (and automake so...
don't angry :) )

When i try to use CommonC++ in my program i get error at linking stage:

t3q@wieprzek:/vol/home/t3q/src/koszty$ make
Making all in src
make[1]: Entering directory `/vol/home/t3q/src/koszty/src'
c++  -g -O2    -o koszty  Main.o -lstdc++ -lccgnu2 -lpthread -ldl
Main.o: In function `basic_string<char, string_char_traits<char>,
__default_alloc_template<true, 0> >::replace(unsigned int, unsigned int,
char const *, unsigned int)':
/usr/lib/gcc-lib/i386-linux/2.95.4/../../../../include/g++-3/std/bastring.cc:156: 

undefined reference to `ost::UnixSocket::UnixSocket(char const *, int)'
collect2: ld returned 1 exit status
make[1]: *** [koszty] Error 1
make[1]: Leaving directory `/vol/home/t3q/src/koszty/src'
make: *** [all-recursive] Error 1
t3q@wieprzek:/vol/home/t3q/src/koszty$

This is my makefile.am:

t3q@wieprzek:/vol/home/t3q/src/koszty/src$ cat Makefile.am
MAINTAINERCLEANFILES = Makefile.in Makefile

CXXFLAGS = @CXXFLAGS@ $(THREAD_FLAGS)
LDADD = -lstdc++ -lccgnu2 -lpthread -ldl

noinst_PROGRAMS = koszty
#koszty_HEADERS =
koszty_SOURCES = Main.cc
koszty_LDADD = $(LDADD)

And this is code:
t3q@wieprzek:/vol/home/t3q/src/koszty/src$ cat Main.cc

#include <cc++/unix.h>

using namespace ost;
using namespace std;

int main ( int argc, char *argv )
{
     UnixSocket *usock;

     usock = new UnixSocket ("my.sock");

     delete usock;

     return 0;
}

Thanx for any help !

Jakub Zawierucha





From MAILER-DAEMON Fri May 02 08:57:55 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19Ba6d-0007Xg-00
	for mharc-bug-commoncpp@gnu.org; Fri, 02 May 2003 08:57:39 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19Ba6H-0006u6-00
	for bug-commoncpp@gnu.org; Fri, 02 May 2003 08:57:17 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19Ba5U-0005xu-00
	for bug-commoncpp@gnu.org; Fri, 02 May 2003 08:56:29 -0400
Received: from pool-138-89-45-96.mad.east.verizon.net ([138.89.45.96]
	helo=home.bayonne.dyndns.org)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 19Ba50-0005hT-00
	for bug-commoncpp@gnu.org; Fri, 02 May 2003 08:55:58 -0400
Received: from 192.168.1.104 ([192.168.1.104])
	by home.bayonne.dyndns.org (8.11.6/8.11.6) with ESMTP id h42DicI18583;
	Fri, 2 May 2003 09:44:38 -0400
From: David Sugar <dyfet@ostel.com>
To: Jakub Zawierucha <Jakub.Zawierucha@nit.pl>, bug-commoncpp@gnu.org
Date: Fri, 2 May 2003 08:45:49 -0400
User-Agent: KMail/1.5
References: <3EB2484A.2030104@nit.pl>
In-Reply-To: <3EB2484A.2030104@nit.pl>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200305020845.49399.dyfet@ostel.com>
Subject: Re: Undefined reference problem on 1.0.9
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 02 May 2003 12:57:37 -0000

"Unix" local socket support is actually in -lccext2, not ccgnu2.  Hence, you 
need to extend your link statement a bit, using the result of 
"ccgnu2-config --stdlibs"


On Friday 02 May 2003 06:28 am, Jakub Zawierucha wrote:
> Hi there... this is my first battle with CommonC++ (and automake so...
> don't angry :) )
>
> When i try to use CommonC++ in my program i get error at linking stage:
>
> t3q@wieprzek:/vol/home/t3q/src/koszty$ make
> Making all in src
> make[1]: Entering directory `/vol/home/t3q/src/koszty/src'
> c++  -g -O2    -o koszty  Main.o -lstdc++ -lccgnu2 -lpthread -ldl
> Main.o: In function `basic_string<char, string_char_traits<char>,
> __default_alloc_template<true, 0> >::replace(unsigned int, unsigned int,
> char const *, unsigned int)':
> /usr/lib/gcc-lib/i386-linux/2.95.4/../../../../include/g++-3/std/bastring.c
>c:156:
>
> undefined reference to `ost::UnixSocket::UnixSocket(char const *, int)'
> collect2: ld returned 1 exit status
> make[1]: *** [koszty] Error 1
> make[1]: Leaving directory `/vol/home/t3q/src/koszty/src'
> make: *** [all-recursive] Error 1
> t3q@wieprzek:/vol/home/t3q/src/koszty$
>
> This is my makefile.am:
>
> t3q@wieprzek:/vol/home/t3q/src/koszty/src$ cat Makefile.am
> MAINTAINERCLEANFILES = Makefile.in Makefile
>
> CXXFLAGS = @CXXFLAGS@ $(THREAD_FLAGS)
> LDADD = -lstdc++ -lccgnu2 -lpthread -ldl
>
> noinst_PROGRAMS = koszty
> #koszty_HEADERS =
> koszty_SOURCES = Main.cc
> koszty_LDADD = $(LDADD)
>
> And this is code:
> t3q@wieprzek:/vol/home/t3q/src/koszty/src$ cat Main.cc
>
> #include <cc++/unix.h>
>
> using namespace ost;
> using namespace std;
>
> int main ( int argc, char *argv )
> {
>      UnixSocket *usock;
>
>      usock = new UnixSocket ("my.sock");
>
>      delete usock;
>
>      return 0;
> }
>
> Thanx for any help !
>
> Jakub Zawierucha
>
>
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp




From MAILER-DAEMON Fri May 02 09:09:18 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19BaGY-0002hI-00
	for mharc-bug-commoncpp@gnu.org; Fri, 02 May 2003 09:07:54 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19BaGG-0002Ce-00
	for bug-commoncpp@gnu.org; Fri, 02 May 2003 09:07:36 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19BaFy-0001vy-00
	for bug-commoncpp@gnu.org; Fri, 02 May 2003 09:07:19 -0400
Received: from pool-138-89-45-96.mad.east.verizon.net ([138.89.45.96]
	helo=home.bayonne.dyndns.org)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 19BaFK-0001ii-00
	for bug-commoncpp@gnu.org; Fri, 02 May 2003 09:06:38 -0400
Received: from 192.168.1.104 ([192.168.1.104])
	by home.bayonne.dyndns.org (8.11.6/8.11.6) with ESMTP id h42DtsI18680;
	Fri, 2 May 2003 09:55:54 -0400
From: David Sugar <dyfet@ostel.com>
To: Dimitar Dimitrov <dimitar@yucom.be>, bug-commoncpp@gnu.org
Date: Fri, 2 May 2003 08:57:05 -0400
User-Agent: KMail/1.5
References: <200305021306.39374.dimitar@yucom.be>
In-Reply-To: <200305021306.39374.dimitar@yucom.be>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200305020857.05182.dyfet@ostel.com>
cc: triendl klaus <triendl.kj@aon.at>
cc: Federico Montesino Pouzols <fedemp@altern.org>
Subject: Re: Problem in ~Thread()
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 02 May 2003 13:07:53 -0000

In "RELEASE1", the posix version of Thread::terminate() checks to see if priv 
is NULL before it tries to do anything else, so this should be okay.  
However, the win32 version does not.  So this I see as the first problem.  In 
fact, from what I see, the win32 version never actually deletes priv or sets 
it to NULL anywhere, which is a different problem.  In "HEAD", sure enough, 
priv->_msgbuf is checked in the destructor without verifying if priv is valid 
first.  In fact, the priv->_msgbuf freeing code probably should be moved into 
terminate itself before it deletes priv (for posix).  For win32, priv 
probably should be deleted at the end of the destructor, and appropriate 
checks added to make sure a NULL priv is not being references.

On Friday 02 May 2003 07:06 am, Dimitar Dimitrov wrote:
> Hi,
>
> I think this is a bug in the Thread class and more precisely in ~Thread().
>
> The problem is that Thread::terminate() deletes and sets Thread::priv to
> NULL. If the destructor of Thread is called afterwards it tries to access
> priv->_msgbuf, whithout checking whether priv == NULL, which results in a
> segmentation fault.
>
> This is exactly what happens in SocketService destructor. It calls
> terminate ( that is Thread::terminate() ) and then ~Thread() is called.
>
> Regards,
> Dimitar
>
>
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp




From MAILER-DAEMON Fri May 02 11:44:32 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19Bchd-0006yb-00
	for mharc-bug-commoncpp@gnu.org; Fri, 02 May 2003 11:44:01 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19BchC-00064W-00
	for bug-commoncpp@gnu.org; Fri, 02 May 2003 11:43:34 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19Bcgs-0005Jv-00
	for bug-commoncpp@gnu.org; Fri, 02 May 2003 11:43:16 -0400
Received: from rusty.kulnet.kuleuven.ac.be ([134.58.240.42])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19BcfI-0003TG-00
	for bug-commoncpp@gnu.org; Fri, 02 May 2003 11:41:36 -0400
Received: from localhost (localhost [127.0.0.1])
	by rusty.kulnet.kuleuven.ac.be (Postfix) with ESMTP
	id D44D41D721D; Fri,  2 May 2003 17:41:34 +0200 (CEST)
Received: from crassus.kulnet.kuleuven.ac.be (crassus.kulnet.kuleuven.ac.be
	[134.58.240.63])	by rusty.kulnet.kuleuven.ac.be (Postfix) with ESMTP
	id 698801D7355; Fri,  2 May 2003 17:41:34 +0200 (CEST)
Received: from 192.168.159.128 (10-67-120-25.kotnet.org [10.67.120.25])
	by crassus.kulnet.kuleuven.ac.be (Postfix) with ESMTP
	id 51A2213EC0E; Fri,  2 May 2003 17:41:33 +0200 (CEST)
From: Dimitar Dimitrov <dimitar@yucom.be>
To: David Sugar <dyfet@ostel.com>, bug-commoncpp@gnu.org
Date: Fri, 2 May 2003 17:41:23 +0200
User-Agent: KMail/1.5.1
References: <200305021306.39374.dimitar@yucom.be>
	<200305020857.05182.dyfet@ostel.com>
In-Reply-To: <200305020857.05182.dyfet@ostel.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="koi8-r"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200305021741.23943.dimitar@yucom.be>
X-Virus-Scanned: by KULeuven Antivirus Cluster
cc: triendl klaus <triendl.kj@aon.at>
cc: Federico Montesino Pouzols <fedemp@altern.org>
Subject: Re: Problem in ~Thread()
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 02 May 2003 15:43:59 -0000

On Friday 02 May 2003 14:57, David Sugar wrote:
> In "RELEASE1", the posix version of Thread::terminate() checks to see if
> priv is NULL before it tries to do anything else, so this should be okay.
> However, the win32 version does not.  So this I see as the first problem. 
> In fact, from what I see, the win32 version never actually deletes priv or
> sets it to NULL anywhere, which is a different problem.  In "HEAD", sure
> enough, priv->_msgbuf is checked in the destructor without verifying if
> priv is valid first.  In fact, the priv->_msgbuf freeing code probably
> should be moved into terminate itself before it deletes priv (for posix). 
> For win32, priv probably should be deleted at the end of the destructor,
> and appropriate checks added to make sure a NULL priv is not being
> references.
>

I forgot to mention it is in "HEAD". I just saw in the cvs you fixed it ;-) 
About moving the cleanup of _msgbuf in terminate() together with other 
cleanup code there, it is may be a good idea. I don't know the initial reason 
to make this in the destructor so I hesitate a bit to comment here.

Something else:
As we are in thread.cpp anyway can somebody add joinSem.post() in 
Thread::close() (in "RELEASE1"). It is in "HEAD" but not in "RELEASE1" so if 
somebody tries to join a thread joinSem.wait() hangs.

Regards,
Dimitar





From MAILER-DAEMON Fri May 02 11:51:53 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19Bcn1-0007PR-00
	for mharc-bug-commoncpp@gnu.org; Fri, 02 May 2003 11:49:35 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19Bc5f-0005gf-00
	for bug-commoncpp@gnu.org; Fri, 02 May 2003 11:04:47 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19Bc56-0004p1-00
	for bug-commoncpp@gnu.org; Fri, 02 May 2003 11:04:12 -0400
Received: from gateway.hns.com ([208.236.67.13])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19Bc4o-0004UN-00
	for bug-commoncpp@gnu.org; Fri, 02 May 2003 11:03:54 -0400
Received: from excore8.hns.com (excore8.hns.com [139.85.52.156])
	h42F3mUk002299
	for <bug-commoncpp@gnu.org>; Fri, 2 May 2003 11:03:49 -0400 (EDT)
Received: from rpppc1.md.hns.com (rpppc1.md.hns.com [139.85.94.36])
	h42F3gnw000855
	for <bug-commoncpp@gnu.org>; Fri, 2 May 2003 11:03:42 -0400 (EDT)
From: "Neal D. Becker" <nbecker@hns.com>
To: bug-commoncpp@gnu.org
Date: Fri, 2 May 2003 11:03:42 -0400
User-Agent: KMail/1.5.1
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200305021103.42541.nbecker@hns.com>
X-Mailman-Approved-At: Fri, 02 May 2003 11:49:34 -0400
Subject: Help with persistence
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 02 May 2003 15:05:43 -0000

Can anyone point me to a simple example of how to use persistence, please?




From MAILER-DAEMON Wed May 07 06:29:08 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19DMAW-00068W-00
	for mharc-bug-commoncpp@gnu.org; Wed, 07 May 2003 06:29:00 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19D9QN-00074n-00
	for bug-commoncpp@gnu.org; Tue, 06 May 2003 16:52:31 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19D99M-00010O-00
	for bug-commoncpp@gnu.org; Tue, 06 May 2003 16:34:58 -0400
Received: from south-labs-dhcp-130-2684.client.mscd.edu ([147.153.56.184]
	helo=laptop)	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19D94d-0008AK-00
	for bug-commoncpp@gnu.org; Tue, 06 May 2003 16:30:03 -0400
Received: from localhost ([127.0.0.1] helo=laptop)
	by laptop with esmtp (Exim 3.36 #1 (Debian))
	id 19D94e-0000Sh-00
	for <bug-commoncpp@gnu.org>; Tue, 06 May 2003 14:30:04 -0600
Date: Tue, 6 May 2003 14:30:03 -0600
From: Nick <nick@jabberstudio.org>
To: bug-commoncpp@gnu.org
Message-ID: <20030506203003.GA1740@laptop.mscd.edu>
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset=ISO-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-Mailer: Balsa 2.0.10
Content-Length: 587
Lines: 15
X-Mailman-Approved-At: Wed, 07 May 2003 06:28:55 -0400
Subject: join mailing list?
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: nick@jabberstudio.org
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 06 May 2003 20:57:06 -0000

I was curious where the mailing list for cc++ is located so I could get 
on it. I have some ideas on the XMLStream class (like _real_ 
incremental parsing instead of depending on a blocking read) and some 
ideas on other areas of cc++ too, like providing thread-safe templates 
(just wraping some of the containers). I'm not sure if I can contribute 
much, but I would like to get involved in some development (since 
ultimately it will help me out). Thanks for the time to read this.

-- 

Nicholas Perez
Email: 	nick@jabberstudio.org
Jabber:	nickperez@jabber.org
Home:	303.759.0574




From MAILER-DAEMON Wed May 07 06:31:58 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19DMAW-00068X-00
	for mharc-bug-commoncpp@gnu.org; Wed, 07 May 2003 06:29:00 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19DL8Z-0006R0-00
	for bug-commoncpp@gnu.org; Wed, 07 May 2003 05:22:55 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19DL89-0005K9-00
	for bug-commoncpp@gnu.org; Wed, 07 May 2003 05:22:32 -0400
Received: from postman.ateme.net ([217.167.236.59])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19DL83-0004tl-00
	for bug-commoncpp@gnu.org; Wed, 07 May 2003 05:22:23 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by postman.ateme.net (Postfix) with ESMTP
	id 475B2280A3; Wed,  7 May 2003 11:22:15 +0200 (CEST)
Received: from pc183 (pc-183.ateme.net [172.16.16.183])
	by postman.ateme.net (Postfix) with SMTP
	id 0E1CF27FDE; Wed,  7 May 2003 11:22:15 +0200 (CEST)
Message-ID: <002b01c3147a$276e94f0$b71010ac@pc183>
From: =?Windows-1252?Q?=C9tienne_Dupuis?= <e.dupuis@ateme.fr>
To: <bug-commoncpp@gnu.org>
Date: Wed, 7 May 2003 11:22:17 +0200
Organization: ATEME
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0028_01C3148A.EAEDC800"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Virus-Scanned: by F-Prot 3.12d
X-Mailman-Approved-At: Wed, 07 May 2003 06:28:55 -0400
cc: =?Windows-1252?Q?Isma=EBl_Djima?= <i.djima@ateme.fr>
Subject: Thread.join() ?
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: =?Windows-1252?Q?=C9tienne_Dupuis?= <e.dupuis@ateme.fr>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 07 May 2003 09:23:31 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0028_01C3148A.EAEDC800
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Greetings,

Method Thread.join() seems to never return. On Linux, with Common C++ =
1.0.9, consider the following program :

int main()
{
    class Wait : public Thread {
        protected :
            virtual void run() {
                sleep(1000);
            }
    };

    Wait wait;
    wait.start();
    wait.join();

    return 0;
}

It never ends as it is stuck in the join() method. However, on Windows =
2000 it works correctly. Moreover, method Thread::yield() yields as much =
as one second (!) on my Linux machine but works as expected on Windows.

Anyone got similar problems ? Should I consider that my Linux kernel is =
the culprit ? Kernel version is 2.4.18-14.

Thanks, =C9tienne Dupuis

------=_NextPart_000_0028_01C3148A.EAEDC800
Content-Type: text/html;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dwindows-1252">
<META content=3D"MSHTML 6.00.2800.1170" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3D"Times New Roman" size=3D2>Greetings,</FONT></DIV>
<DIV><FONT face=3D"Times New Roman" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"Times New Roman" size=3D2>Method Thread.join() seems =
to never=20
return. On Linux, with Common C++ 1.0.9, consider the following program=20
:</FONT></DIV>
<DIV><FONT face=3D"Times New Roman" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"Times New Roman" size=3D2>int main()</FONT></DIV>
<DIV><FONT face=3D"Times New Roman" size=3D2>{</FONT></DIV>
<DIV><FONT face=3D"Times New Roman" size=3D2>&nbsp;&nbsp;&nbsp; class =
Wait : public=20
Thread {</FONT></DIV>
<DIV><FONT face=3D"Times New Roman" size=3D2>&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
protected :</FONT></DIV>
<DIV><FONT face=3D"Times New Roman" size=3D2>&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; virtual void run() {</FONT></DIV>
<DIV><FONT face=3D"Times New Roman" size=3D2>&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; sleep(1000);</FONT></DIV>
<DIV><FONT face=3D"Times New Roman" size=3D2>&nbsp;&nbsp;&nbsp; =
&nbsp;&nbsp;&nbsp;=20
&nbsp;&nbsp;&nbsp; }</FONT></DIV>
<DIV><FONT face=3D"Times New Roman" size=3D2>&nbsp;&nbsp;&nbsp; =
};</FONT></DIV>
<DIV><FONT face=3D"Times New Roman" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"Times New Roman" size=3D2>&nbsp;&nbsp;&nbsp; Wait=20
wait;</FONT></DIV>
<DIV><FONT face=3D"Times New Roman" size=3D2>&nbsp;&nbsp;&nbsp;=20
wait.start();</FONT></DIV>
<DIV><FONT face=3D"Times New Roman" size=3D2>&nbsp;&nbsp;&nbsp;=20
wait.join();</FONT></DIV>
<DIV><FONT face=3D"Times New Roman" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"Times New Roman" size=3D2>&nbsp;&nbsp;&nbsp; return=20
0;</FONT></DIV>
<DIV><FONT face=3D"Times New Roman" size=3D2>}</FONT></DIV>
<DIV><FONT face=3D"Times New Roman" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"Times New Roman" size=3D2>It never ends as it is =
stuck in the=20
join() method. However, on Windows 2000 it works correctly. </FONT><FONT =

face=3D"Times New Roman" size=3D2>Moreover, method Thread::yield() =
yields as much as=20
one second (!) on my Linux machine but works as expected on=20
Windows.</FONT></DIV>
<DIV><FONT face=3D"Times New Roman" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"Times New Roman" size=3D2>Anyone got similar problems =
? Should I=20
consider that my Linux kernel is the culprit ? Kernel version is=20
2.4.18-14.</FONT></DIV>
<DIV><FONT face=3D"Times New Roman" size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3D"Times New Roman" size=3D2>Thanks, =C9tienne =
Dupuis</FONT></DIV>
<DIV><FONT face=3D"Times New Roman" =
size=3D2></FONT>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_0028_01C3148A.EAEDC800--




From MAILER-DAEMON Thu May 08 07:46:52 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19DjqQ-00023b-00
	for mharc-bug-commoncpp@gnu.org; Thu, 08 May 2003 07:45:50 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19Dhmt-0002AX-00
	for bug-commoncpp@gnu.org; Thu, 08 May 2003 05:34:03 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19Dhms-000280-00
	for bug-commoncpp@gnu.org; Thu, 08 May 2003 05:34:02 -0400
Received: from cvis163.marconicomms.com ([128.87.251.113])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19Dhmr-000212-00
	for bug-commoncpp@gnu.org; Thu, 08 May 2003 05:34:01 -0400
Received: from cvis153.mail.marconicomms.com by cvis163.marconicomms.com with
	ESMTP	(8.11.6+Sun/mcig-3) id h489XvE01561;
	Thu, 8 May 2003 10:33:57 +0100 (BST)
Received: from cvdgwy01.uk.marconicomms.com (unverified) by 
    cvis151.mail.marconicomms.com (Content Technologies SMTPRS 4.3.6) with 
    ESMTP id <T6213bad8bdc0a899e12b4@cvis151.mail.marconicomms.com> for 
    <bug-commoncpp@gnu.org>; Thu, 8 May 2003 10:30:07 +0100
To: bug-commoncpp@gnu.org
X-Mailer: Lotus Notes Release 5.0.8  June 18, 2001
Message-ID: <OF8220BF83.0A64D39F-ONC1256D20.002D4B06@uk.marconicomms.com>
From: "Georg Soffel" <Georg.Soffel@marconi.com>
Date: Thu, 8 May 2003 10:54:04 +0200
X-MIMETrack: Serialize by Router on CVDGWY01/S/EXT/MC1 
    (Release 5.0.12  |February 13, 2003) at 08/05/2003 10:30:00
MIME-Version: 1.0
Content-type: text/plain; charset="us-ascii"
X-Mailman-Approved-At: Thu, 08 May 2003 07:45:48 -0400
Subject: Incoming data loss due to TCPStream::sync(void) gettting called if
 the a tcpstream is flushed!
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 08 May 2003 09:34:04 -0000


Hello all,

I am using the tcpstream class in binary mode:

    mystream.setf(ios::binary);
    mystream.unsetf(ios::skipws);

I wrote stream operators for a message class
which are used to send and receive messages via the stream socket, like :

  mystream >> msg;

for receiving a message from the stream and:

  mystream << msg << flush;

for sending a message to the stream.

Now I noticed an incoming message loss. Further investigations showed that
the reason was due to the fact that the call to flush led to a call of the
sync function
in the TCPStream class. This was not what I expected! I wanted only to get
the
message send immediately by the flush and not clear my incoming buffer.
I am not an expert with steam and stream buffer classes in the Standard C++
Library but I think this is not the desired behaviour.

I solved the problem by writing my own "Flush" function:

class mytcpstream : public tcpstream {
public:
    void Flush(void) {   // flush without clearing the incoming buffer
            overflow(EOF);
    }
    Error setNoDelay(bool enable) {   // disable nagle for better
performance
            return Socket::setNoDelay(enable);
    }
};

Now

  mystream << msg; mystream.Flush();

works fine without any message loss even under high load.


Please give me some feedback/comments. This problem probably also
occurs if the stream is not used in binary mode and "endl" is used!

Regards
Georg Soffel

Marconi Communications GmbH    Phone: +49 (7191) 13    2155
Postfach: 1920                                       Fax:       +49 (7191)
13 6 2155
D-71509 Backnang
mailto:Georg.Soffel@marconi.com
Germany






From MAILER-DAEMON Sun May 11 09:28:52 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19Eqsf-0000te-00
	for mharc-bug-commoncpp@gnu.org; Sun, 11 May 2003 09:28:45 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19EqsS-0000Zx-00
	for bug-commoncpp@gnu.org; Sun, 11 May 2003 09:28:32 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19Eqs6-0008K4-00
	for bug-commoncpp@gnu.org; Sun, 11 May 2003 09:28:11 -0400
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19Eqrk-0007rE-00
	for bug-commoncpp@gnu.org; Sun, 11 May 2003 09:27:48 -0400
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 19EqyC-0008RL-00; Sun, 11 May 2003 15:34:28 +0200
Date: Sun, 11 May 2003 15:34:28 +0200
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Nick <nick@jabberstudio.org>
Message-ID: <20030511133428.GB23836@bulbasaur.rediris.es>
Mail-Followup-To: Nick <nick@jabberstudio.org>, bug-commoncpp@gnu.org
References: <20030506203003.GA1740@laptop.mscd.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030506203003.GA1740@laptop.mscd.edu>
User-Agent: Mutt/1.5.4i
Sender: Federico Montesino Pouzols <fedemp@bulbasaur.rediris.es>
cc: bug-commoncpp@gnu.org
Subject: Re: join mailing list?
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 11 May 2003 13:28:44 -0000


	Well, this is the mailing list :). Good, we are always open
for new ideas, so go ahead.

On Tue, May 06, 2003 at 02:30:03PM -0600, Nick wrote:
> I was curious where the mailing list for cc++ is located so I could get 
> on it. I have some ideas on the XMLStream class (like _real_ 
> incremental parsing instead of depending on a blocking read) and some 
> ideas on other areas of cc++ too, like providing thread-safe templates 
> (just wraping some of the containers). I'm not sure if I can contribute 
> much, but I would like to get involved in some development (since 
> ultimately it will help me out). Thanks for the time to read this.
> 
> -- 
> 
> Nicholas Perez
> Email: 	nick@jabberstudio.org
> Jabber:	nickperez@jabber.org
> Home:	303.759.0574
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From MAILER-DAEMON Sun May 11 09:37:02 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19Er0G-0007MQ-00
	for mharc-bug-commoncpp@gnu.org; Sun, 11 May 2003 09:36:36 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19EqYE-0000Ty-00
	for bug-commoncpp@gnu.org; Sun, 11 May 2003 09:07:38 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19EqVz-0007gq-00
	for bug-commoncpp@gnu.org; Sun, 11 May 2003 09:05:19 -0400
Received: from subversions.gnu.org ([199.232.41.2])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19EqSm-0006CS-00
	for bug-commoncpp@gnu.org; Sun, 11 May 2003 09:02:00 -0400
Received: from www-data by subversions.gnu.org with local (Exim 3.35 #1
	(Debian))	id 19EqSw-0001kW-00; Sun, 11 May 2003 09:02:10 -0400
To: bug-commoncpp@gnu.org,awagger@web.de,fedemp@altern.org
From: nobody@savannah.gnu.org
Message-Id: <E19EqSw-0001kW-00@subversions.gnu.org>
Date: Sun, 11 May 2003 09:02:10 -0400
X-Mailman-Approved-At: Sun, 11 May 2003 09:36:33 -0400
Subject: [Bug #3315] problems with ftp code in Borland C++ Builder
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 11 May 2003 13:10:20 -0000


=================== BUG #3315: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3315&group_id=89

Changes by: Federico Montesino Pouzols <fedemp@altern.org>
Date: Sun 05/11/2003 at 15:02 (Europe/Madrid)

            What     | Removed                   | Added
---------------------------------------------------------------------------
          Resolution | None                      | Later
         Assigned to | None                      | fedemp
                  CC |                           | bug-commoncpp@gnu.org


------------------ Additional Follow-up Comments ----------------------------

 The second issue is fixed in CVS. As for the first one, I
suspect that your proposed change will break the library on
other platforms. Does anyone know if this happens because of
the istream implementation of Borland c++?.




=================== BUG #3315: FULL BUG SNAPSHOT ===================


Submitted by: awagger                 Project: commonc++                    
Submitted on: Thu 04/24/2003 at 00:36
Category:  None                       Severity:  5 - Major                  
Bug Group:  None                      Resolution:  Later                    
Assigned to:  fedemp                  Status:  Open                         

Summary:  problems with ftp code in Borland C++ Builder

Original Submission:  I found (and fixed) two problems with the ftp code in libcommonc++2-1.0.9 when using the Borland C++ Builder (version 5).

1) I had to comment out line ftp.cpp:647 in method FTPSocket::DirEntry::parse(string li):

    str.get();  // skip space

since the mentioned space seemed to be included in the variable "junk", filled in the line bevore (ftp.cpp:646):

    str >> access >> junk >> user >> group >> size >> junk >> junk >> junk;


I don't know if it is an istream operator implementation problem or a unix <-> windows problem.


2) I had to change line ftp.cpp:482:

    ofstream f( lfilename.c_str() );

by explicitly specifying binary output mode like this:

    ofstream f( lfilename.c_str(),
        std::ios::out|std::ios::trunc|std::ios::binary );

otherwise the char '\n' got written as two bytes (as usual in windows in text-mode). So this is clearly a unix <-> windows porting problem. But I think, it should be perfectly ok, to use the same code for unix, since the result should be the same.



Follow-up Comments
*******************

-------------------------------------------------------
Date: Sun 05/11/2003 at 15:02       By: fedemp

 The second issue is fixed in CVS. As for the first one, I
suspect that your proposed change will break the library on
other platforms. Does anyone know if this happens because of
the istream implementation of Borland c++?.



CC List
*******

CC Address                          | Comment
------------------------------------+-----------------------------
bug-commoncpp@gnu.org               | 



No files currently attached


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3315&group_id=89



From MAILER-DAEMON Sun May 11 09:37:20 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19Er0G-0007MY-00
	for mharc-bug-commoncpp@gnu.org; Sun, 11 May 2003 09:36:36 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19EqfN-0006Hs-00
	for bug-commoncpp@gnu.org; Sun, 11 May 2003 09:15:01 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19Eqf4-00064E-00
	for bug-commoncpp@gnu.org; Sun, 11 May 2003 09:14:42 -0400
Received: from subversions.gnu.org ([199.232.41.2])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19Eqed-0005r5-00
	for bug-commoncpp@gnu.org; Sun, 11 May 2003 09:14:15 -0400
Received: from www-data by subversions.gnu.org with local (Exim 3.35 #1
	(Debian))	id 19Eqen-00020U-00; Sun, 11 May 2003 09:14:25 -0400
To: bug-commoncpp@gnu.org,savannah.email@tracker.drzoom.ch,fedemp@altern.org
From: nobody@savannah.gnu.org
Message-Id: <E19Eqen-00020U-00@subversions.gnu.org>
Date: Sun, 11 May 2003 09:14:25 -0400
X-Mailman-Approved-At: Sun, 11 May 2003 09:36:33 -0400
Subject: [Bug #3289] Function missing, v2 1.0.9, Datetime::Datetime( time_t tm
	)
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 11 May 2003 13:18:57 -0000


=================== BUG #3289: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3289&group_id=89

Changes by: Federico Montesino Pouzols <fedemp@altern.org>
Date: Sun 05/11/2003 at 15:14 (Europe/Madrid)

            What     | Removed                   | Added
---------------------------------------------------------------------------
          Resolution | None                      | Later
         Assigned to | None                      | fedemp
                  CC |                           | bug-commoncpp@gnu.org


------------------ Additional Follow-up Comments ----------------------------

 Is this method missing for any particular reason I am not
able to see, or it simply was forgotten? In the latter case,
its implementation should be as simple as the implementation
of the constructor without parameters.



=================== BUG #3289: FULL BUG SNAPSHOT ===================


Submitted by: drzoom                  Project: commonc++                    
Submitted on: Mon 04/21/2003 at 14:42
Category:  None                       Severity:  5 - Major                  
Bug Group:  None                      Resolution:  Later                    
Assigned to:  fedemp                  Status:  Open                         

Summary:  Function missing, v2 1.0.9, Datetime::Datetime( time_t tm )

Original Submission:  This Function is currently missing, but declared in the header.

Follow-up Comments
*******************

-------------------------------------------------------
Date: Sun 05/11/2003 at 15:14       By: fedemp

 Is this method missing for any particular reason I am not
able to see, or it simply was forgotten? In the latter case,
its implementation should be as simple as the implementation
of the constructor without parameters.


CC List
*******

CC Address                          | Comment
------------------------------------+-----------------------------
bug-commoncpp@gnu.org               | 



No files currently attached


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3289&group_id=89



From MAILER-DAEMON Sun May 11 09:37:55 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19Er0F-0007Ln-00
	for mharc-bug-commoncpp@gnu.org; Sun, 11 May 2003 09:36:35 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19Eq7R-0004gY-00
	for bug-commoncpp@gnu.org; Sun, 11 May 2003 08:39:57 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19Eq7Q-0004gL-00
	for bug-commoncpp@gnu.org; Sun, 11 May 2003 08:39:56 -0400
Received: from subversions.gnu.org ([199.232.41.2])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19Eq7P-0004gF-00
	for bug-commoncpp@gnu.org; Sun, 11 May 2003 08:39:55 -0400
Received: from www-data by subversions.gnu.org with local (Exim 3.35 #1
	(Debian))	id 19Eq7Z-0001HF-00; Sun, 11 May 2003 08:40:05 -0400
To: bug-commoncpp@gnu.org,fedemp@altern.org
From: nobody@savannah.gnu.org
Message-Id: <E19Eq7Z-0001HF-00@subversions.gnu.org>
Date: Sun, 11 May 2003 08:40:05 -0400
X-Mailman-Approved-At: Sun, 11 May 2003 09:36:33 -0400
Subject: [Bug #3284] cvs build broken
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 11 May 2003 12:39:57 -0000


=================== BUG #3284: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3284&group_id=89

Changes by: Federico Montesino Pouzols <fedemp@altern.org>
Date: Sun 05/11/2003 at 14:40 (Europe/Madrid)

            What     | Removed                   | Added
---------------------------------------------------------------------------
          Resolution | None                      | Fixed
         Assigned to | None                      | fedemp
              Status | Open                      | Closed
                  CC |                           | bug-commoncpp@gnu.org


------------------ Additional Follow-up Comments ----------------------------
This was fixed in CVS a few days ago.



=================== BUG #3284: FULL BUG SNAPSHOT ===================


Submitted by: None                    Project: commonc++                    
Submitted on: Mon 04/21/2003 at 04:33
Category:  None                       Severity:  5 - Major                  
Bug Group:  None                      Resolution:  Fixed                    
Assigned to:  fedemp                  Status:  Closed                       

Summary:  cvs build broken

Original Submission:  Commoncpp2 RELEASE1 does not build.

compat-libstdc++-6.2-2.9.0.16
libstdc++-2.96-98
libstdc++-devel-2.96-98
gcc-c++-2.96-98

cvs command:

cvs -z3 -d :pserver:anoncvs@subversions.gnu.org:/cvsroot/commoncpp co
-rRELEASE1 commoncpp2

Output of make attached.

Follow-up Comments
*******************

-------------------------------------------------------
Date: Sun 05/11/2003 at 14:40       By: fedemp
This was fixed in CVS a few days ago.


CC List
*******

CC Address                          | Comment
------------------------------------+-----------------------------
bug-commoncpp@gnu.org               | 



File Attachments
****************

-------------------------------------------------------
Date: Mon 04/21/2003 at 04:33  Name: ccpp2bug.txt  Size: 1KB   By: None
make output
http://savannah.gnu.org/bugs/download.php?group_id=89&amp;bug_id=3284&amp;bug_file_id=403


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3284&group_id=89



From MAILER-DAEMON Sun May 11 09:38:41 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19Er0F-0007Li-00
	for mharc-bug-commoncpp@gnu.org; Sun, 11 May 2003 09:36:35 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19Eq2t-0005sK-00
	for bug-commoncpp@gnu.org; Sun, 11 May 2003 08:35:15 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19Eq2Y-0005iF-00
	for bug-commoncpp@gnu.org; Sun, 11 May 2003 08:34:55 -0400
Received: from subversions.gnu.org ([199.232.41.2])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19Eq24-0005XP-00
	for bug-commoncpp@gnu.org; Sun, 11 May 2003 08:34:24 -0400
Received: from www-data by subversions.gnu.org with local (Exim 3.35 #1
	(Debian))	id 19Eq2D-00017g-00; Sun, 11 May 2003 08:34:33 -0400
To: bug-commoncpp@gnu.org,savannah.email@tracker.drzoom.ch,fedemp@altern.org
From: nobody@savannah.gnu.org
Message-Id: <E19Eq2D-00017g-00@subversions.gnu.org>
Date: Sun, 11 May 2003 08:34:33 -0400
X-Mailman-Approved-At: Sun, 11 May 2003 09:36:33 -0400
Subject: [Bug #3290] const's Missing, v2 1.0.9, class Datetime
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 11 May 2003 12:35:35 -0000


=================== BUG #3290: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3290&group_id=89

Changes by: Federico Montesino Pouzols <fedemp@altern.org>
Date: Sun 05/11/2003 at 14:34 (Europe/Madrid)

            What     | Removed                   | Added
---------------------------------------------------------------------------
          Resolution | None                      | Fixed
         Assigned to | None                      | fedemp
              Status | Open                      | Closed
                  CC |                           | bug-commoncpp@gnu.org


------------------ Additional Follow-up Comments ----------------------------

Fixed in CVS.



=================== BUG #3290: FULL BUG SNAPSHOT ===================


Submitted by: drzoom                  Project: commonc++                    
Submitted on: Mon 04/21/2003 at 14:46
Category:  None                       Severity:  5 - Major                  
Bug Group:  None                      Resolution:  Fixed                    
Assigned to:  fedemp                  Status:  Closed                       

Summary:  const's Missing, v2 1.0.9, class Datetime

Original Submission:  All constant functions should be declaed as "const".

class Foo {
	protected:
		Datetime datetime;
	public:
		const Datetime& getDatetime() const
		{
			return datetime;
		}
}

main()
{
	Foo foo;
	
	// ERROR: because the missing const declarations...
	cout << foo.getDatetime().strftime( "%T" ) << endl;
}


Follow-up Comments
*******************

-------------------------------------------------------
Date: Sun 05/11/2003 at 14:34       By: fedemp

Fixed in CVS.


CC List
*******

CC Address                          | Comment
------------------------------------+-----------------------------
bug-commoncpp@gnu.org               | 



No files currently attached


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3290&group_id=89



From MAILER-DAEMON Tue May 13 15:02:26 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19Ff2f-0006Jb-00
	for mharc-bug-commoncpp@gnu.org; Tue, 13 May 2003 15:02:25 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19Ff2d-0006JI-00
	for bug-commoncpp@gnu.org; Tue, 13 May 2003 15:02:23 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19Ff2b-0006Id-00
	for bug-commoncpp@gnu.org; Tue, 13 May 2003 15:02:22 -0400
Received: from acate.com.br ([200.215.17.89] helo=cli004.brasmap)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19Ff29-00066T-00
	for bug-commoncpp@gnu.org; Tue, 13 May 2003 15:01:53 -0400
Received: from cli004.brasmap (localhost.localdomain [127.0.0.1])
	by cli004.brasmap (Postfix) with SMTP id 78C135B926
	for <bug-commoncpp@gnu.org>; Tue, 13 May 2003 16:01:28 -0300 (BRT)
Date: Tue, 13 May 2003 16:01:22 -0300
From: Marcelo Dalmas <mad@brasmap.com.br>
To: ccxx <bug-commoncpp@gnu.org>
Message-Id: <20030513160122.43c52c89.mad@brasmap.com.br>
Organization: BRASMAP Siatemas, Consultoria e =?ISO-8859-1?Q?Com=E9rcio?=
 LTDA.
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i586-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: multipart/signed; protocol="application/pgp-signature";
 micalg="pgp-sha1"; boundary="=.XMWHTw(yUy.kp9"
Subject: None
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 13 May 2003 19:02:24 -0000

--=.XMWHTw(yUy.kp9
Content-Type: multipart/mixed;
 boundary="Multipart_Tue__13_May_2003_16:01:22_-0300_08261ec8"


--Multipart_Tue__13_May_2003_16:01:22_-0300_08261ec8
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable


Hi all,

I'm sending a patch with operator for Datetime.

By,

--=20
-------------------------------------------------
  Marcelo Dalmas - Eng. de Controle e Automa=E7=E3o
-------------------------------------------------
  BRASMAP Sistemas, Consultoria e Com=E9rcio Ltda.
        Engenharia em Aquisi=E7=E3o de Dados

     www.brasmap.com.br - info@brasmap.com.br
Fone: (48) 333-2218 ramal 2114 Fax: (48) 333-3745
-------------------------------------------------


--Multipart_Tue__13_May_2003_16:01:22_-0300_08261ec8
Content-Type: application/octet-stream;
 name="datetime-20030513.patch"
Content-Disposition: attachment;
 filename="datetime-20030513.patch"
Content-Transfer-Encoding: base64

SW5kZXg6IGluY2x1ZGUvY2MrKy9udW1iZXJzLmgKPT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQpSQ1MgZmlsZTogL3Vzci9s
b2NhbC9jdnNyb290L2JyYXNtYXAvY29tbW9uY3BwMi9pbmNsdWRlL2NjKysvbnVtYmVycy5oLHYK
cmV0cmlldmluZyByZXZpc2lvbiAxLjcKZGlmZiAtdSAtcjEuNyBudW1iZXJzLmgKLS0tIGluY2x1
ZGUvY2MrKy9udW1iZXJzLmgJMjAwMy8wMi8xMCAxMjoxODoxMwkxLjcKKysrIGluY2x1ZGUvY2Mr
Ky9udW1iZXJzLmgJMjAwMy8wNS8xMyAxNzozMTo1NgpAQCAtMjg0LDYgKzI4NCwxNSBAQAogCURh
dGV0aW1lJiBvcGVyYXRvci09KERhdGV0aW1lICZkYXRldGltZSk7CiAJRGF0ZXRpbWUmIG9wZXJh
dG9yKz0oVGltZSAmdGltZSk7CiAJRGF0ZXRpbWUmIG9wZXJhdG9yLT0oVGltZSAmdGltZSk7CisK
KwlpbnQgb3BlcmF0b3I9PShEYXRldGltZSYpOworCWludCBvcGVyYXRvciE9KERhdGV0aW1lJik7
CisJaW50IG9wZXJhdG9yPChEYXRldGltZSYpOworCWludCBvcGVyYXRvcjw9KERhdGV0aW1lJik7
CisJaW50IG9wZXJhdG9yPihEYXRldGltZSYpOworCWludCBvcGVyYXRvcj49KERhdGV0aW1lJik7
CisJYm9vbCBvcGVyYXRvciEoKTsKKwogCXN0ZDo6c3RyaW5nIHN0cmZ0aW1lKGNvbnN0IGNoYXIg
KmZvcm1hdCk7CiB9OwogCkluZGV4OiBzcmMvZGF0ZS5jcHAKPT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQpSQ1MgZmlsZTog
L3Vzci9sb2NhbC9jdnNyb290L2JyYXNtYXAvY29tbW9uY3BwMi9zcmMvZGF0ZS5jcHAsdgpyZXRy
aWV2aW5nIHJldmlzaW9uIDEuMTQKZGlmZiAtdSAtcjEuMTQgZGF0ZS5jcHAKLS0tIHNyYy9kYXRl
LmNwcAkyMDAzLzA0LzIyIDEyOjIzOjEzCTEuMTQKKysrIHNyYy9kYXRlLmNwcAkyMDAzLzA1LzEz
IDE3OjI4OjMzCkBAIC04MjksNiArODI5LDYzIEBACiAJcmV0dXJuICp0aGlzOwogfQogCitpbnQg
RGF0ZXRpbWU6Om9wZXJhdG9yPT0oRGF0ZXRpbWUgJmQpCit7CisJcmV0dXJuIChqdWxpYW4gPT0g
ZC5qdWxpYW4pICYmIChzZWNvbmRzID09IGQuc2Vjb25kcyk7Cit9CisKK2ludCBEYXRldGltZTo6
b3BlcmF0b3IhPShEYXRldGltZSAmZCkKK3sKKwlyZXR1cm4gKGp1bGlhbiAhPSBkLmp1bGlhbikg
fHwgKHNlY29uZHMgIT0gZC5zZWNvbmRzKTsKK30KKworaW50IERhdGV0aW1lOjpvcGVyYXRvcjwo
RGF0ZXRpbWUgJmQpCit7CisJaWYgKGp1bGlhbiAhPSBkLmp1bGlhbikgeworCQlyZXR1cm4gKGp1
bGlhbiA8IGQuanVsaWFuKTsKKwl9CisJZWxzZSB7CisJCXJldHVybiAoc2Vjb25kcyA8IGQuc2Vj
b25kcyk7CisJfQorfQorCitpbnQgRGF0ZXRpbWU6Om9wZXJhdG9yPD0oRGF0ZXRpbWUgJmQpCit7
CisJaWYgKGp1bGlhbiAhPSBkLmp1bGlhbikgeworCQlyZXR1cm4gKGp1bGlhbiA8IGQuanVsaWFu
KTsKKwl9CisJZWxzZSB7CisJCXJldHVybiAoc2Vjb25kcyA8PSBkLnNlY29uZHMpOworCX0KK30K
KworaW50IERhdGV0aW1lOjpvcGVyYXRvcj4oRGF0ZXRpbWUgJmQpCit7CisJaWYgKGp1bGlhbiAh
PSBkLmp1bGlhbikgeworCQlyZXR1cm4gKGp1bGlhbiA+IGQuanVsaWFuKTsKKwl9CisJZWxzZSB7
CisJCXJldHVybiAoc2Vjb25kcyA+IGQuc2Vjb25kcyk7CisJfQorfQorCitpbnQgRGF0ZXRpbWU6
Om9wZXJhdG9yPj0oRGF0ZXRpbWUgJmQpCit7CisJaWYgKGp1bGlhbiAhPSBkLmp1bGlhbikgewor
CQlyZXR1cm4gKGp1bGlhbiA+IGQuanVsaWFuKTsKKwl9CisJZWxzZSB7CisJCXJldHVybiAoc2Vj
b25kcyA+PSBkLnNlY29uZHMpOworCX0KK30KKworYm9vbCBEYXRldGltZTo6b3BlcmF0b3IhKCkK
K3sKKwlyZXR1cm4gIShEYXRlOjppc1ZhbGlkKCkgJiYgVGltZTo6aXNWYWxpZCgpKTsKK30KKwor
CisKIHN0cmluZyBEYXRldGltZTo6c3RyZnRpbWUoY29uc3QgY2hhciAqZm9ybWF0KQogewogCWNo
YXIgYnVmZmVyWzY0XTsK

--Multipart_Tue__13_May_2003_16:01:22_-0300_08261ec8--

--=.XMWHTw(yUy.kp9
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE+wUEH95NRejZp8BwRAuDOAKCByHfL7zt1jEhFatYNgVDGfu2eKwCgreoD
TApTDArzYjmx5pOZXxDj/qo=
=xob1
-----END PGP SIGNATURE-----

--=.XMWHTw(yUy.kp9--



From MAILER-DAEMON Wed May 14 04:28:47 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19FrZT-0004Bh-00
	for mharc-bug-commoncpp@gnu.org; Wed, 14 May 2003 04:25:07 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19FrZQ-0004BK-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 04:25:04 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19FrZO-0004B8-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 04:25:03 -0400
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19FrYI-0003gc-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 04:23:54 -0400
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 19Fret-0003Rm-00; Wed, 14 May 2003 10:30:43 +0200
Date: Wed, 14 May 2003 10:30:43 +0200
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Marcelo Dalmas <mad@brasmap.com.br>
Message-ID: <20030514083043.GC5529@bulbasaur.rediris.es>
Mail-Followup-To: Marcelo Dalmas <mad@brasmap.com.br>,
	bug-commoncpp@gnu.org
References: <20030513160122.43c52c89.mad@brasmap.com.br>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20030513160122.43c52c89.mad@brasmap.com.br>
User-Agent: Mutt/1.5.4i
Sender: Federico Montesino Pouzols <fedemp@altern.org>
cc: bug-commoncpp@gnu.org
Subject: Re: None (Operators for Datetime)
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 14 May 2003 08:25:05 -0000


	Hi, it is in CVS. Did you see 'Bug 3289' at Savannah? Last
Sunday I sent a comment on it to the list; do you agree?

On Tue, May 13, 2003 at 04:01:22PM -0300, Marcelo Dalmas wrote:
> 
> Hi all,
> 
> I'm sending a patch with operator for Datetime.
> 
> By,
> 
> -- 
> -------------------------------------------------
>   Marcelo Dalmas - Eng. de Controle e Automação
> -------------------------------------------------
>   BRASMAP Sistemas, Consultoria e Comércio Ltda.
>         Engenharia em Aquisição de Dados
> 
>      www.brasmap.com.br - info@brasmap.com.br
> Fone: (48) 333-2218 ramal 2114 Fax: (48) 333-3745
> -------------------------------------------------
> 





> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp




From MAILER-DAEMON Wed May 14 04:53:09 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19FrwS-0007Hd-00
	for mharc-bug-commoncpp@gnu.org; Wed, 14 May 2003 04:48:52 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19FrvR-000668-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 04:47:49 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19FruT-0005al-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 04:46:52 -0400
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19Frt6-0004lb-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 04:45:24 -0400
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 19Frzf-0003dc-00; Wed, 14 May 2003 10:52:11 +0200
Date: Wed, 14 May 2003 10:52:11 +0200
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Dimitar Dimitrov <dimitar@yucom.be>
Message-ID: <20030514085211.GA13266@bulbasaur.rediris.es>
Mail-Followup-To: Dimitar Dimitrov <dimitar@yucom.be>,
	David Sugar <dyfet@ostel.com>, bug-commoncpp@gnu.org,
	triendl klaus <triendl.kj@aon.at>
References: <200305021306.39374.dimitar@yucom.be>
	<200305020857.05182.dyfet@ostel.com> <200305021741.23943.dimitar@yucom.be>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200305021741.23943.dimitar@yucom.be>
User-Agent: Mutt/1.5.4i
Sender: Federico Montesino Pouzols <fedemp@altern.org>
cc: triendl klaus <triendl.kj@aon.at>
cc: bug-commoncpp@gnu.org
cc: David Sugar <dyfet@ostel.com>
Subject: Re: Problem in ~Thread()
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 14 May 2003 08:48:50 -0000


	It has just been added.

On Fri, May 02, 2003 at 05:41:23PM +0200, Dimitar Dimitrov wrote:
>
> Something else:
> As we are in thread.cpp anyway can somebody add joinSem.post() in 
> Thread::close() (in "RELEASE1"). It is in "HEAD" but not in "RELEASE1" so if 
> somebody tries to join a thread joinSem.wait() hangs.
> 
> Regards,
> Dimitar
> 
> 



From MAILER-DAEMON Wed May 14 07:21:18 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19Ftnh-00011R-00
	for mharc-bug-commoncpp@gnu.org; Wed, 14 May 2003 06:47:57 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19Ftil-00085n-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 06:42:51 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19FtfC-0007Uw-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 06:39:11 -0400
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19FtSX-0003if-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 06:26:06 -0400
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 19FtZB-00043m-00; Wed, 14 May 2003 12:32:57 +0200
Date: Wed, 14 May 2003 12:32:57 +0200
From: Federico Montesino Pouzols <fedemp@altern.org>
To: David Sugar <dyfet@ostel.com>
Message-ID: <20030514103257.GA15377@bulbasaur.rediris.es>
Mail-Followup-To: David Sugar <dyfet@ostel.com>, bug-commoncpp@gnu.org
References: <Pine.LNX.4.44.0304231828202.1218-100000@MainServer.bksys.co.in>
	<200304231207.11412.dyfet@ostel.com>
	<20030424070945.GA17757@bulbasaur.rediris.es>
	<200304240757.31484.dyfet@ostel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200304240757.31484.dyfet@ostel.com>
User-Agent: Mutt/1.5.4i
Sender: Federico Montesino Pouzols <fedemp@altern.org>
cc: bug-commoncpp@gnu.org
Subject: Re: [Ccrtp-devel] Compile error - ccrtp 1.0.0
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 14 May 2003 10:47:56 -0000


	Let's move this issue to bug-commoncpp...

	I like this idea. Should we release 1.0.10 once we fix the
bugs that are pending, and then go to 1.1.0 (with the new socketport
stuff)?

On Thu, Apr 24, 2003 at 07:57:31AM -0400, David Sugar wrote:
> Done.
> 
> I also have a new and better idea for handling of the socketport constructor 
> change (and the other recent 1.0.x changes related to macosx).  Let's make 
> the next release from the "RELEASE1" tree 1.1.0 with the socketport changes, 
> and move "HEAD" into a future "1.9" or similar release...This gives a clear 
> delination in release for something that will change backward compatibility.
> 



From MAILER-DAEMON Wed May 14 07:29:49 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19FuOo-0007Qo-00
	for mharc-bug-commoncpp@gnu.org; Wed, 14 May 2003 07:26:18 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19Feea-0003Nn-00
	for bug-commoncpp@gnu.org; Tue, 13 May 2003 14:37:32 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19FecE-0001Bj-00
	for bug-commoncpp@gnu.org; Tue, 13 May 2003 14:35:08 -0400
Received: from acate.com.br ([200.215.17.89] helo=cli004.brasmap)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19FeZq-0007bP-00
	for bug-commoncpp@gnu.org; Tue, 13 May 2003 14:32:38 -0400
Received: from cli004.brasmap (localhost.localdomain [127.0.0.1])
	by cli004.brasmap (Postfix) with SMTP id D41E25B926
	for <bug-commoncpp@gnu.org>; Tue, 13 May 2003 15:32:08 -0300 (BRT)
Date: Tue, 13 May 2003 15:32:03 -0300
From: Marcelo Dalmas <marcelo@brasmap.com.br>
To: ccxx <bug-commoncpp@gnu.org>
Message-Id: <20030513153203.0e510132.marcelo@brasmap.com.br>
Organization: BRASMAP Siatemas, Consultoria e =?ISO-8859-1?Q?Com=E9rcio?=
 LTDA.
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i586-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: multipart/signed; protocol="application/pgp-signature";
 micalg="pgp-sha1"; boundary="=.nImD7wfgUkLq8D"
X-Mailman-Approved-At: Wed, 14 May 2003 07:26:15 -0400
Subject: Operators for Datetime
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 13 May 2003 18:37:59 -0000

--=.nImD7wfgUkLq8D
Content-Type: multipart/mixed;
 boundary="Multipart_Tue__13_May_2003_15:32:03_-0300_08224c60"


--Multipart_Tue__13_May_2003_15:32:03_-0300_08224c60
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi all,

I'm sending a patch with operator for Datetime.

By,

--=20
-------------------------------------------------
  Marcelo Dalmas - Eng. de Controle e Automa=E7=E3o
-------------------------------------------------
  BRASMAP Sistemas, Consultoria e Com=E9rcio Ltda.
        Engenharia em Aquisi=E7=E3o de Dados

     www.brasmap.com.br - info@brasmap.com.br
Fone: (48) 333-2218 ramal 2114 Fax: (48) 333-3745
-------------------------------------------------


--Multipart_Tue__13_May_2003_15:32:03_-0300_08224c60
Content-Type: application/octet-stream;
 name="datetime-20030513.patch"
Content-Disposition: attachment;
 filename="datetime-20030513.patch"
Content-Transfer-Encoding: base64

SW5kZXg6IGluY2x1ZGUvY2MrKy9udW1iZXJzLmgKPT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQpSQ1MgZmlsZTogL3Vzci9s
b2NhbC9jdnNyb290L2JyYXNtYXAvY29tbW9uY3BwMi9pbmNsdWRlL2NjKysvbnVtYmVycy5oLHYK
cmV0cmlldmluZyByZXZpc2lvbiAxLjcKZGlmZiAtdSAtcjEuNyBudW1iZXJzLmgKLS0tIGluY2x1
ZGUvY2MrKy9udW1iZXJzLmgJMjAwMy8wMi8xMCAxMjoxODoxMwkxLjcKKysrIGluY2x1ZGUvY2Mr
Ky9udW1iZXJzLmgJMjAwMy8wNS8xMyAxNzozMTo1NgpAQCAtMjg0LDYgKzI4NCwxNSBAQAogCURh
dGV0aW1lJiBvcGVyYXRvci09KERhdGV0aW1lICZkYXRldGltZSk7CiAJRGF0ZXRpbWUmIG9wZXJh
dG9yKz0oVGltZSAmdGltZSk7CiAJRGF0ZXRpbWUmIG9wZXJhdG9yLT0oVGltZSAmdGltZSk7CisK
KwlpbnQgb3BlcmF0b3I9PShEYXRldGltZSYpOworCWludCBvcGVyYXRvciE9KERhdGV0aW1lJik7
CisJaW50IG9wZXJhdG9yPChEYXRldGltZSYpOworCWludCBvcGVyYXRvcjw9KERhdGV0aW1lJik7
CisJaW50IG9wZXJhdG9yPihEYXRldGltZSYpOworCWludCBvcGVyYXRvcj49KERhdGV0aW1lJik7
CisJYm9vbCBvcGVyYXRvciEoKTsKKwogCXN0ZDo6c3RyaW5nIHN0cmZ0aW1lKGNvbnN0IGNoYXIg
KmZvcm1hdCk7CiB9OwogCkluZGV4OiBzcmMvZGF0ZS5jcHAKPT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQpSQ1MgZmlsZTog
L3Vzci9sb2NhbC9jdnNyb290L2JyYXNtYXAvY29tbW9uY3BwMi9zcmMvZGF0ZS5jcHAsdgpyZXRy
aWV2aW5nIHJldmlzaW9uIDEuMTQKZGlmZiAtdSAtcjEuMTQgZGF0ZS5jcHAKLS0tIHNyYy9kYXRl
LmNwcAkyMDAzLzA0LzIyIDEyOjIzOjEzCTEuMTQKKysrIHNyYy9kYXRlLmNwcAkyMDAzLzA1LzEz
IDE3OjI4OjMzCkBAIC04MjksNiArODI5LDYzIEBACiAJcmV0dXJuICp0aGlzOwogfQogCitpbnQg
RGF0ZXRpbWU6Om9wZXJhdG9yPT0oRGF0ZXRpbWUgJmQpCit7CisJcmV0dXJuIChqdWxpYW4gPT0g
ZC5qdWxpYW4pICYmIChzZWNvbmRzID09IGQuc2Vjb25kcyk7Cit9CisKK2ludCBEYXRldGltZTo6
b3BlcmF0b3IhPShEYXRldGltZSAmZCkKK3sKKwlyZXR1cm4gKGp1bGlhbiAhPSBkLmp1bGlhbikg
fHwgKHNlY29uZHMgIT0gZC5zZWNvbmRzKTsKK30KKworaW50IERhdGV0aW1lOjpvcGVyYXRvcjwo
RGF0ZXRpbWUgJmQpCit7CisJaWYgKGp1bGlhbiAhPSBkLmp1bGlhbikgeworCQlyZXR1cm4gKGp1
bGlhbiA8IGQuanVsaWFuKTsKKwl9CisJZWxzZSB7CisJCXJldHVybiAoc2Vjb25kcyA8IGQuc2Vj
b25kcyk7CisJfQorfQorCitpbnQgRGF0ZXRpbWU6Om9wZXJhdG9yPD0oRGF0ZXRpbWUgJmQpCit7
CisJaWYgKGp1bGlhbiAhPSBkLmp1bGlhbikgeworCQlyZXR1cm4gKGp1bGlhbiA8IGQuanVsaWFu
KTsKKwl9CisJZWxzZSB7CisJCXJldHVybiAoc2Vjb25kcyA8PSBkLnNlY29uZHMpOworCX0KK30K
KworaW50IERhdGV0aW1lOjpvcGVyYXRvcj4oRGF0ZXRpbWUgJmQpCit7CisJaWYgKGp1bGlhbiAh
PSBkLmp1bGlhbikgeworCQlyZXR1cm4gKGp1bGlhbiA+IGQuanVsaWFuKTsKKwl9CisJZWxzZSB7
CisJCXJldHVybiAoc2Vjb25kcyA+IGQuc2Vjb25kcyk7CisJfQorfQorCitpbnQgRGF0ZXRpbWU6
Om9wZXJhdG9yPj0oRGF0ZXRpbWUgJmQpCit7CisJaWYgKGp1bGlhbiAhPSBkLmp1bGlhbikgewor
CQlyZXR1cm4gKGp1bGlhbiA+IGQuanVsaWFuKTsKKwl9CisJZWxzZSB7CisJCXJldHVybiAoc2Vj
b25kcyA+PSBkLnNlY29uZHMpOworCX0KK30KKworYm9vbCBEYXRldGltZTo6b3BlcmF0b3IhKCkK
K3sKKwlyZXR1cm4gIShEYXRlOjppc1ZhbGlkKCkgJiYgVGltZTo6aXNWYWxpZCgpKTsKK30KKwor
CisKIHN0cmluZyBEYXRldGltZTo6c3RyZnRpbWUoY29uc3QgY2hhciAqZm9ybWF0KQogewogCWNo
YXIgYnVmZmVyWzY0XTsK

--Multipart_Tue__13_May_2003_15:32:03_-0300_08224c60--

--=.nImD7wfgUkLq8D
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE+wToo95NRejZp8BwRAjCCAJ0eLCp9hMCl3VPppN5R29tqTr3hNgCePbGN
+eamCmAQCufu+dHyf6qjX1Q=
=1Ruf
-----END PGP SIGNATURE-----

--=.nImD7wfgUkLq8D--



From MAILER-DAEMON Wed May 14 07:31:16 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19FuOp-0007Qw-00
	for mharc-bug-commoncpp@gnu.org; Wed, 14 May 2003 07:26:19 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19FuBe-0003hl-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 07:12:42 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19FuAS-0003MH-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 07:11:29 -0400
Received: from subversions.gnu.org ([199.232.41.2])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19Fu3b-0001z2-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 07:04:23 -0400
Received: from www-data by subversions.gnu.org with local (Exim 3.35 #1
	(Debian))	id 19Fu3l-0002kG-00; Wed, 14 May 2003 07:04:33 -0400
To: bug-commoncpp@gnu.org,peter.karl.mueller@gmx.de,fedemp@altern.org
From: nobody@savannah.gnu.org
Message-Id: <E19Fu3l-0002kG-00@subversions.gnu.org>
Date: Wed, 14 May 2003 07:04:33 -0400
X-Mailman-Approved-At: Wed, 14 May 2003 07:26:15 -0400
Subject: [Bug #3279] refman: 8.91 Thread Class Reference:
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 14 May 2003 11:18:01 -0000


=================== BUG #3279: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3279&group_id=89

Changes by: Federico Montesino Pouzols <fedemp@altern.org>
Date: Wed 05/14/03 at 13:04 (Europe/Madrid)

------------------ Additional Follow-up Comments ----------------------------
As for Bug #1754, I have not been able to get the
same behaviour you describe, but similar crashes in
some platforms. We will look at it, as well as other
problems with threads. If you have more info or even
a trace, it would be very useful for us.




=================== BUG #3279: FULL BUG SNAPSHOT ===================


Submitted by: None                    Project: commonc++                    
Submitted on: Sun 04/20/03 at 13:47
Category:  None                       Severity:  5 - Major                  
Bug Group:  None                      Resolution:  None                     
Assigned to:  fedemp                  Status:  Open                         

Summary:  refman: 8.91 Thread Class Reference:

Original Submission:  The reference manual says:

"Every thread of execution in an application is created by
 deriving a unique class from the Thread class and by
 implementing the Run method. base class used to derive all
 threads of execution."

This is IMHO wrong. Since you have at compile time a
fixed number of classes you could only get a fixed number
of threads. This is not the case (or?). AFAICS a thread
is created each time a run method is executed after a
derived class has been instanciated.

Follow-up Comments
*******************

-------------------------------------------------------
Date: Wed 05/14/03 at 13:04         By: fedemp
As for Bug #1754, I have not been able to get the
same behaviour you describe, but similar crashes in
some platforms. We will look at it, as well as other
problems with threads. If you have more info or even
a trace, it would be very useful for us.


-------------------------------------------------------
Date: Wed 05/14/03 at 13:03         By: fedemp
As for Bug #1754, I have not been able to get the
same behaviour you describe, but similar crashes in
some platforms. We will look at it, as well as other
problems with threads. If you have more info or even
a trace, it would be very useful for us.


-------------------------------------------------------
Date: Wed 05/14/03 at 12:59         By: fedemp

The thread is created when start() or detach() is called.
The constructors of the Thread class just initialize
resources.


-------------------------------------------------------
Date: Wed 05/14/03 at 12:34         By: pkm
[BTW: What about #1754? can nobody reproduce it?]

-------------------------------------------------------
Date: Wed 05/14/03 at 12:32         By: pkm
When exactly is the thread created? Is is created
when the objects constructor is finished or during
the excecution of start ()? 

-------------------------------------------------------
Date: Wed 05/14/03 at 11:53         By: fedemp

 Um, yes it seems that the explanation may be a bit confusing.

 Do you agree with replacing:

"by deriving a unique class from the Thread class and by
implementing the Run method."

with

"by instantiating an object of a class derived from the
Thread class. Classes derived from Thread must implement
the method run, which specifies the code of the thread."


-------------------------------------------------------
Date: Sun 04/20/03 at 13:49         By: pkm
[sorry, did not logged in]


CC List
*******

CC Address                          | Comment
------------------------------------+-----------------------------
bug-commoncpp@gnu.org               | 
peter.karl.mueller@gmx.de           | ()



No files currently attached


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3279&group_id=89



From MAILER-DAEMON Wed May 14 07:31:18 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19FuOp-0007Qv-00
	for mharc-bug-commoncpp@gnu.org; Wed, 14 May 2003 07:26:19 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19Ftf3-0007Nh-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 06:39:01 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19Ftbe-000688-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 06:35:41 -0400
Received: from subversions.gnu.org ([199.232.41.2])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19FtaJ-0005Uk-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 06:34:07 -0400
Received: from www-data by subversions.gnu.org with local (Exim 3.35 #1
	(Debian))	id 19FtaS-0001ou-00; Wed, 14 May 2003 06:34:16 -0400
To: bug-commoncpp@gnu.org,peter.karl.mueller@gmx.de,fedemp@altern.org
From: nobody@savannah.gnu.org
Message-Id: <E19FtaS-0001ou-00@subversions.gnu.org>
Date: Wed, 14 May 2003 06:34:16 -0400
X-Mailman-Approved-At: Wed, 14 May 2003 07:26:15 -0400
Subject: [Bug #3279] refman: 8.91 Thread Class Reference:
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 14 May 2003 10:43:07 -0000


=================== BUG #3279: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3279&group_id=89

Changes by: Peter Karl Müller <peter.karl.mueller@gmx.de>
Date: Wed 05/14/2003 at 12:34 (Europe/Berlin)

------------------ Additional Follow-up Comments ----------------------------
[BTW: What about #1754? can nobody reproduce it?]



=================== BUG #3279: FULL BUG SNAPSHOT ===================


Submitted by: None                    Project: commonc++                    
Submitted on: Sun 04/20/2003 at 13:47
Category:  None                       Severity:  5 - Major                  
Bug Group:  None                      Resolution:  None                     
Assigned to:  None                    Status:  Open                         

Summary:  refman: 8.91 Thread Class Reference:

Original Submission:  The reference manual says:

"Every thread of execution in an application is created by
 deriving a unique class from the Thread class and by
 implementing the Run method. base class used to derive all
 threads of execution."

This is IMHO wrong. Since you have at compile time a
fixed number of classes you could only get a fixed number
of threads. This is not the case (or?). AFAICS a thread
is created each time a run method is executed after a
derived class has been instanciated.

Follow-up Comments
*******************

-------------------------------------------------------
Date: Wed 05/14/2003 at 12:34       By: pkm
[BTW: What about #1754? can nobody reproduce it?]

-------------------------------------------------------
Date: Wed 05/14/2003 at 12:32       By: pkm
When exactly is the thread created? Is is created
when the objects constructor is finished or during
the excecution of start ()? 

-------------------------------------------------------
Date: Wed 05/14/2003 at 11:53       By: fedemp

 Um, yes it seems that the explanation may be a bit confusing.

 Do you agree with replacing:

"by deriving a unique class from the Thread class and by
implementing the Run method."

with

"by instantiating an object of a class derived from the
Thread class. Classes derived from Thread must implement
the method run, which specifies the code of the thread."


-------------------------------------------------------
Date: Sun 04/20/2003 at 13:49       By: pkm
[sorry, did not logged in]


CC List
*******

CC Address                          | Comment
------------------------------------+-----------------------------
bug-commoncpp@gnu.org               | 
peter.karl.mueller@gmx.de           | ()



No files currently attached


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3279&group_id=89



From MAILER-DAEMON Wed May 14 07:31:24 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19FuOp-0007Qu-00
	for mharc-bug-commoncpp@gnu.org; Wed, 14 May 2003 07:26:19 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19Fsx9-0007Bz-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 05:53:39 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19Fswx-0006ig-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 05:53:29 -0400
Received: from subversions.gnu.org ([199.232.41.2])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19Fswm-0006Tb-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 05:53:16 -0400
Received: from www-data by subversions.gnu.org with local (Exim 3.35 #1
	(Debian))	id 19Fsww-0006Ob-00; Wed, 14 May 2003 05:53:26 -0400
To: bug-commoncpp@gnu.org,peter.karl.mueller@gmx.de,fedemp@altern.org
From: nobody@savannah.gnu.org
Message-Id: <E19Fsww-0006Ob-00@subversions.gnu.org>
Date: Wed, 14 May 2003 05:53:26 -0400
X-Mailman-Approved-At: Wed, 14 May 2003 07:26:15 -0400
Subject: [Bug #3279] refman: 8.91 Thread Class Reference:
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 14 May 2003 09:54:01 -0000


=================== BUG #3279: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3279&group_id=89

Changes by: Federico Montesino Pouzols <fedemp@altern.org>
Date: Wed 05/14/03 at 11:53 (Europe/Madrid)

            What     | Removed                   | Added
---------------------------------------------------------------------------
                  CC |                           | bug-commoncpp@gnu.org


------------------ Additional Follow-up Comments ----------------------------

 Um, yes it seems that the explanation may be a bit confusing.

 Do you agree with replacing:

"by deriving a unique class from the Thread class and by
implementing the Run method."

with

"by instantiating an object of a class derived from the
Thread class. Classes derived from Thread must implement
the method run, which specifies the code of the thread."




=================== BUG #3279: FULL BUG SNAPSHOT ===================


Submitted by: None                    Project: commonc++                    
Submitted on: Sun 04/20/03 at 13:47
Category:  None                       Severity:  5 - Major                  
Bug Group:  None                      Resolution:  None                     
Assigned to:  None                    Status:  Open                         

Summary:  refman: 8.91 Thread Class Reference:

Original Submission:  The reference manual says:

"Every thread of execution in an application is created by
 deriving a unique class from the Thread class and by
 implementing the Run method. base class used to derive all
 threads of execution."

This is IMHO wrong. Since you have at compile time a
fixed number of classes you could only get a fixed number
of threads. This is not the case (or?). AFAICS a thread
is created each time a run method is executed after a
derived class has been instanciated.

Follow-up Comments
*******************

-------------------------------------------------------
Date: Wed 05/14/03 at 11:53         By: fedemp

 Um, yes it seems that the explanation may be a bit confusing.

 Do you agree with replacing:

"by deriving a unique class from the Thread class and by
implementing the Run method."

with

"by instantiating an object of a class derived from the
Thread class. Classes derived from Thread must implement
the method run, which specifies the code of the thread."


-------------------------------------------------------
Date: Sun 04/20/03 at 13:49         By: pkm
[sorry, did not logged in]


CC List
*******

CC Address                          | Comment
------------------------------------+-----------------------------
bug-commoncpp@gnu.org               | 
peter.karl.mueller@gmx.de           | ()



No files currently attached


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3279&group_id=89



From MAILER-DAEMON Wed May 14 07:31:43 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19FuOp-0007Qx-00
	for mharc-bug-commoncpp@gnu.org; Wed, 14 May 2003 07:26:19 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19FuIn-0005JX-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 07:20:05 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19FuBH-0003YW-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 07:12:20 -0400
Received: from subversions.gnu.org ([199.232.41.2])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19FtyU-0001rO-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 06:59:06 -0400
Received: from www-data by subversions.gnu.org with local (Exim 3.35 #1
	(Debian))	id 19Ftyd-0002aL-00; Wed, 14 May 2003 06:59:15 -0400
To: bug-commoncpp@gnu.org,peter.karl.mueller@gmx.de,fedemp@altern.org
From: nobody@savannah.gnu.org
Message-Id: <E19Ftyd-0002aL-00@subversions.gnu.org>
Date: Wed, 14 May 2003 06:59:15 -0400
X-Mailman-Approved-At: Wed, 14 May 2003 07:26:15 -0400
Subject: [Bug #3279] refman: 8.91 Thread Class Reference:
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 14 May 2003 11:21:55 -0000


=================== BUG #3279: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3279&group_id=89

Changes by: Federico Montesino Pouzols <fedemp@altern.org>
Date: Wed 05/14/03 at 12:59 (Europe/Madrid)

            What     | Removed                   | Added
---------------------------------------------------------------------------
         Assigned to | None                      | fedemp


------------------ Additional Follow-up Comments ----------------------------

The thread is created when start() or detach() is called.
The constructors of the Thread class just initialize
resources.




=================== BUG #3279: FULL BUG SNAPSHOT ===================


Submitted by: None                    Project: commonc++                    
Submitted on: Sun 04/20/03 at 13:47
Category:  None                       Severity:  5 - Major                  
Bug Group:  None                      Resolution:  None                     
Assigned to:  fedemp                  Status:  Open                         

Summary:  refman: 8.91 Thread Class Reference:

Original Submission:  The reference manual says:

"Every thread of execution in an application is created by
 deriving a unique class from the Thread class and by
 implementing the Run method. base class used to derive all
 threads of execution."

This is IMHO wrong. Since you have at compile time a
fixed number of classes you could only get a fixed number
of threads. This is not the case (or?). AFAICS a thread
is created each time a run method is executed after a
derived class has been instanciated.

Follow-up Comments
*******************

-------------------------------------------------------
Date: Wed 05/14/03 at 12:59         By: fedemp

The thread is created when start() or detach() is called.
The constructors of the Thread class just initialize
resources.


-------------------------------------------------------
Date: Wed 05/14/03 at 12:34         By: pkm
[BTW: What about #1754? can nobody reproduce it?]

-------------------------------------------------------
Date: Wed 05/14/03 at 12:32         By: pkm
When exactly is the thread created? Is is created
when the objects constructor is finished or during
the excecution of start ()? 

-------------------------------------------------------
Date: Wed 05/14/03 at 11:53         By: fedemp

 Um, yes it seems that the explanation may be a bit confusing.

 Do you agree with replacing:

"by deriving a unique class from the Thread class and by
implementing the Run method."

with

"by instantiating an object of a class derived from the
Thread class. Classes derived from Thread must implement
the method run, which specifies the code of the thread."


-------------------------------------------------------
Date: Sun 04/20/03 at 13:49         By: pkm
[sorry, did not logged in]


CC List
*******

CC Address                          | Comment
------------------------------------+-----------------------------
bug-commoncpp@gnu.org               | 
peter.karl.mueller@gmx.de           | ()



No files currently attached


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3279&group_id=89



From MAILER-DAEMON Wed May 14 07:32:02 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19FuOp-0007Qs-00
	for mharc-bug-commoncpp@gnu.org; Wed, 14 May 2003 07:26:19 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19Fs8J-00061O-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 05:01:07 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19Fs5X-0004sS-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 04:58:15 -0400
Received: from subversions.gnu.org ([199.232.41.2])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19Fs5S-0004or-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 04:58:10 -0400
Received: from www-data by subversions.gnu.org with local (Exim 3.35 #1
	(Debian))	id 19Fs5c-00007I-00; Wed, 14 May 2003 04:58:20 -0400
To: bug-commoncpp@gnu.org,ittay@qlusters.com,fedemp@altern.org
From: nobody@savannah.gnu.org
Message-Id: <E19Fs5c-00007I-00@subversions.gnu.org>
Date: Wed, 14 May 2003 04:58:20 -0400
X-Mailman-Approved-At: Wed, 14 May 2003 07:26:15 -0400
Subject: [Bug #3541] StringTokenizer::iterator memory leak
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 14 May 2003 09:04:50 -0000


=================== BUG #3541: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3541&group_id=89

Changes by: Federico Montesino Pouzols <fedemp@altern.org>
Date: Wed 05/14/03 at 10:58 (Europe/Madrid)

            What     | Removed                   | Added
---------------------------------------------------------------------------
          Resolution | None                      | Fixed
         Assigned to | None                      | fedemp
              Status | Open                      | Closed
                  CC |                           | bug-commoncpp@gnu.org


------------------ Additional Follow-up Comments ----------------------------
It is fixed in CVS.




=================== BUG #3541: FULL BUG SNAPSHOT ===================


Submitted by: ittay                   Project: commonc++                    
Submitted on: Sun 05/11/03 at 16:40
Category:  None                       Severity:  5 - Major                  
Bug Group:  None                      Resolution:  Fixed                    
Assigned to:  fedemp                  Status:  Closed                       

Summary:  StringTokenizer::iterator memory leak

Original Submission:  operator= doesn't delete the token (just sets it to 0), so if operator* was called, the memory that was assigned to token is lost.

Follow-up Comments
*******************

-------------------------------------------------------
Date: Wed 05/14/03 at 10:58         By: fedemp
It is fixed in CVS.



CC List
*******

CC Address                          | Comment
------------------------------------+-----------------------------
bug-commoncpp@gnu.org               | 



No files currently attached


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3541&group_id=89



From MAILER-DAEMON Wed May 14 07:47:11 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19Fuhu-0007Te-00
	for mharc-bug-commoncpp@gnu.org; Wed, 14 May 2003 07:46:02 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19FuVR-0001aA-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 07:33:09 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19FuUT-00018p-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 07:32:10 -0400
Received: from pool-138-89-45-96.mad.east.verizon.net ([138.89.45.96]
	helo=home.bayonne.dyndns.org)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 19FuRR-0008PB-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 07:29:01 -0400
Received: from ostel.com ([192.168.1.100])
	by home.bayonne.dyndns.org (8.11.6/8.11.6) with ESMTP id h4ECJLF00631;
	Wed, 14 May 2003 08:19:21 -0400
Message-ID: <3EC2287C.2070803@ostel.com>
Date: Wed, 14 May 2003 07:29:00 -0400
From: David Sugar <dyfet@ostel.com>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
	rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Federico Montesino Pouzols <fedemp@altern.org>
References: <Pine.LNX.4.44.0304231828202.1218-100000@MainServer.bksys.co.in>
	<200304231207.11412.dyfet@ostel.com>
	<20030424070945.GA17757@bulbasaur.rediris.es>
	<200304240757.31484.dyfet@ostel.com>
	<20030514103257.GA15377@bulbasaur.rediris.es>
In-Reply-To: <20030514103257.GA15377@bulbasaur.rediris.es>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
cc: bug-commoncpp@gnu.org
Subject: Re: [Ccrtp-devel] Compile error - ccrtp 1.0.0
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 14 May 2003 11:45:59 -0000

Yes.  Let's get 1.0.10 out with the current round of bug fixes (and the 
freebsd/macosx build fixes).  I think the SocketPort changes should be a 
distinct minor (1.1.x) since they are not backward compatible.  cvs 
"head" can then move to 1.2.x or later...

Federico Montesino Pouzols wrote:

>	Let's move this issue to bug-commoncpp...
>
>	I like this idea. Should we release 1.0.10 once we fix the
>bugs that are pending, and then go to 1.1.0 (with the new socketport
>stuff)?
>
>On Thu, Apr 24, 2003 at 07:57:31AM -0400, David Sugar wrote:
>  
>
>>Done.
>>
>>I also have a new and better idea for handling of the socketport constructor 
>>change (and the other recent 1.0.x changes related to macosx).  Let's make 
>>the next release from the "RELEASE1" tree 1.1.0 with the socketport changes, 
>>and move "HEAD" into a future "1.9" or similar release...This gives a clear 
>>delination in release for something that will change backward compatibility.
>>
>>    
>>
>
>
>_______________________________________________
>Bug-commoncpp mailing list
>Bug-commoncpp@gnu.org
>http://mail.gnu.org/mailman/listinfo/bug-commoncpp
>  
>




From MAILER-DAEMON Wed May 14 07:48:43 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19Fuiz-0008Qi-00
	for mharc-bug-commoncpp@gnu.org; Wed, 14 May 2003 07:47:09 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19Fuc6-0004gL-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 07:40:02 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19Fub1-0004GF-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 07:38:55 -0400
Received: from pool-138-89-45-96.mad.east.verizon.net ([138.89.45.96]
	helo=home.bayonne.dyndns.org)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 19FuaC-0003qE-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 07:38:04 -0400
Received: from ostel.com ([192.168.1.100])
	by home.bayonne.dyndns.org (8.11.6/8.11.6) with ESMTP id h4ECSIF00683;
	Wed, 14 May 2003 08:28:18 -0400
Message-ID: <3EC22A95.8010209@ostel.com>
Date: Wed, 14 May 2003 07:37:57 -0400
From: David Sugar <dyfet@ostel.com>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
	rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Federico Montesino Pouzols <fedemp@altern.org>
References: <200305021306.39374.dimitar@yucom.be>
	<200305021741.23943.dimitar@yucom.be>
	<20030514085211.GA13266@bulbasaur.rediris.es>
In-Reply-To: <20030514085211.GA13266@bulbasaur.rediris.es>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: triendl klaus <triendl.kj@aon.at>
cc: bug-commoncpp@gnu.org
Subject: Re: Problem in ~Thread()
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 14 May 2003 11:47:07 -0000

Did this also take care of "priv" not being deleted when a win32 thread 
is deleted?

Federico Montesino Pouzols wrote:

>	It has just been added.
>
>On Fri, May 02, 2003 at 05:41:23PM +0200, Dimitar Dimitrov wrote:
>  
>
>>Something else:
>>As we are in thread.cpp anyway can somebody add joinSem.post() in 
>>Thread::close() (in "RELEASE1"). It is in "HEAD" but not in "RELEASE1" so if 
>>somebody tries to join a thread joinSem.wait() hangs.
>>
>>Regards,
>>Dimitar
>>
>>
>>    
>>
>
>
>_______________________________________________
>Bug-commoncpp mailing list
>Bug-commoncpp@gnu.org
>http://mail.gnu.org/mailman/listinfo/bug-commoncpp
>  
>




From MAILER-DAEMON Wed May 14 07:58:10 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19Fuqk-0002q5-00
	for mharc-bug-commoncpp@gnu.org; Wed, 14 May 2003 07:55:10 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19Fuq8-0002YD-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 07:54:32 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19Fult-0000rS-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 07:50:10 -0400
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19FufH-0006Af-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 07:43:19 -0400
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 19Fuly-00047r-00; Wed, 14 May 2003 13:50:14 +0200
Date: Wed, 14 May 2003 13:50:14 +0200
From: Federico Montesino Pouzols <fedemp@altern.org>
To: David Sugar <dyfet@ostel.com>
Message-ID: <20030514115014.GD5529@bulbasaur.rediris.es>
Mail-Followup-To: David Sugar <dyfet@ostel.com>,
	Dimitar Dimitrov <dimitar@yucom.be>,
	triendl klaus <triendl.kj@aon.at>, bug-commoncpp@gnu.org
References: <200305021306.39374.dimitar@yucom.be>
	<200305021741.23943.dimitar@yucom.be>
	<20030514085211.GA13266@bulbasaur.rediris.es> <3EC22A95.8010209@ostel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3EC22A95.8010209@ostel.com>
User-Agent: Mutt/1.5.4i
Sender: Federico Montesino Pouzols <fedemp@altern.org>
cc: triendl klaus <triendl.kj@aon.at>
cc: bug-commoncpp@gnu.org
Subject: Re: Problem in ~Thread()
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 14 May 2003 11:55:08 -0000


	No, I will take care of that a bit later.

On Wed, May 14, 2003 at 07:37:57AM -0400, David Sugar wrote:
> Did this also take care of "priv" not being deleted when a win32 thread 
> is deleted?
> 
> Federico Montesino Pouzols wrote:
> 
> >	It has just been added.
> >
> >On Fri, May 02, 2003 at 05:41:23PM +0200, Dimitar Dimitrov wrote:
> > 
> >
> >>Something else:
> >>As we are in thread.cpp anyway can somebody add joinSem.post() in 
> >>Thread::close() (in "RELEASE1"). It is in "HEAD" but not in "RELEASE1" so 
> >>if somebody tries to join a thread joinSem.wait() hangs.
> >>
> >>Regards,
> >>Dimitar
> >>
> >>
> >>   
> >>
> >
> >
> >_______________________________________________
> >Bug-commoncpp mailing list
> >Bug-commoncpp@gnu.org
> >http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> > 
> >
> 



From MAILER-DAEMON Wed May 14 07:58:50 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19Fukb-0000dk-00
	for mharc-bug-commoncpp@gnu.org; Wed, 14 May 2003 07:48:49 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19FukP-0000YN-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 07:48:37 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19Fuhu-0007Tk-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 07:46:04 -0400
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19Fuh9-0007BL-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 07:45:16 -0400
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 19Funr-000481-00; Wed, 14 May 2003 13:52:11 +0200
Date: Wed, 14 May 2003 13:52:11 +0200
From: Federico Montesino Pouzols <fedemp@altern.org>
To: David Sugar <dyfet@ostel.com>
Message-ID: <20030514115211.GE5529@bulbasaur.rediris.es>
Mail-Followup-To: David Sugar <dyfet@ostel.com>, bug-commoncpp@gnu.org
References: <Pine.LNX.4.44.0304231828202.1218-100000@MainServer.bksys.co.in>
	<200304231207.11412.dyfet@ostel.com>
	<20030424070945.GA17757@bulbasaur.rediris.es>
	<200304240757.31484.dyfet@ostel.com>
	<20030514103257.GA15377@bulbasaur.rediris.es> <3EC229E9.2070407@ostel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3EC229E9.2070407@ostel.com>
User-Agent: Mutt/1.5.4i
Sender: Federico Montesino Pouzols <fedemp@altern.org>
cc: bug-commoncpp@gnu.org
Subject: Re: [Ccrtp-devel] Compile error - ccrtp 1.0.0
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 14 May 2003 11:48:47 -0000


	There is possibly a bug that limits the number of creatable
threads, though it does not occur on all platforms. It has been
reported through the bug tracking system of Savannah.

On Wed, May 14, 2003 at 07:35:05AM -0400, David Sugar wrote:
> In fact, I would like to see 1.0.10 out by the end of the week.  I think 
> the pending issues I was working on related to builds are now closed.  
> There is still a strange problem with redhat and nptl related soley to 
> suspend and resume, but it's not a fatel flaw since all my regular apps 
> build and run.  In fact rh9 is broken since nptl is only fully 
> compatible with kernel late 2.5 kernels (or 2.6), and they still have 
> 2.4 which doesn't fully support it.  But that's another story...
> 
> I saw we had some new bugs filter through, the most interesting being a 
> memory leak in stringtokenizer.  I think that the win32 thread 
> destructor should delete priv.  Other than that, what else is left?
> 
> Federico Montesino Pouzols wrote:
> 
> >	Let's move this issue to bug-commoncpp...
> >
> >	I like this idea. Should we release 1.0.10 once we fix the
> >bugs that are pending, and then go to 1.1.0 (with the new socketport
> >stuff)?
> >
> >On Thu, Apr 24, 2003 at 07:57:31AM -0400, David Sugar wrote:
> > 
> >
> >>Done.
> >>
> >>I also have a new and better idea for handling of the socketport 
> >>constructor change (and the other recent 1.0.x changes related to 
> >>macosx).  Let's make the next release from the "RELEASE1" tree 1.1.0 with 
> >>the socketport changes, and move "HEAD" into a future "1.9" or similar 
> >>release...This gives a clear delination in release for something that 
> >>will change backward compatibility.
> >>
> >>   
> >>
> >
> >
> >_______________________________________________
> >Bug-commoncpp mailing list
> >Bug-commoncpp@gnu.org
> >http://mail.gnu.org/mailman/listinfo/bug-commoncpp
> > 
> >
> 



From MAILER-DAEMON Wed May 14 10:03:28 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19FwfP-0005NC-00
	for mharc-bug-commoncpp@gnu.org; Wed, 14 May 2003 09:51:35 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19FuUA-0000y6-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 07:31:50 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19FuNp-0007EP-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 07:25:19 -0400
Received: from subversions.gnu.org ([199.232.41.2])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19FuLi-0006Fu-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 07:23:06 -0400
Received: from www-data by subversions.gnu.org with local (Exim 3.35 #1
	(Debian))	id 19FuLn-000521-00; Wed, 14 May 2003 07:23:11 -0400
To: bug-commoncpp@gnu.org,peter.karl.mueller@gmx.de,fedemp@altern.org
From: nobody@savannah.gnu.org
Message-Id: <E19FuLn-000521-00@subversions.gnu.org>
Date: Wed, 14 May 2003 07:23:11 -0400
X-Mailman-Approved-At: Wed, 14 May 2003 09:51:33 -0400
Subject: [Bug #3279] refman: 8.91 Thread Class Reference:
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 14 May 2003 11:32:36 -0000


=================== BUG #3279: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3279&group_id=89

Changes by: Peter Karl Müller <peter.karl.mueller@gmx.de>
Date: Wed 05/14/2003 at 13:23 (Europe/Berlin)

------------------ Additional Follow-up Comments ----------------------------
Sorry. No need to give an example since there is already
one. The number of threads is still limited.



=================== BUG #3279: FULL BUG SNAPSHOT ===================


Submitted by: None                    Project: commonc++                    
Submitted on: Sun 04/20/2003 at 13:47
Category:  None                       Severity:  5 - Major                  
Bug Group:  None                      Resolution:  None                     
Assigned to:  fedemp                  Status:  Open                         

Summary:  refman: 8.91 Thread Class Reference:

Original Submission:  The reference manual says:

"Every thread of execution in an application is created by
 deriving a unique class from the Thread class and by
 implementing the Run method. base class used to derive all
 threads of execution."

This is IMHO wrong. Since you have at compile time a
fixed number of classes you could only get a fixed number
of threads. This is not the case (or?). AFAICS a thread
is created each time a run method is executed after a
derived class has been instanciated.

Follow-up Comments
*******************

-------------------------------------------------------
Date: Wed 05/14/2003 at 13:23       By: pkm
Sorry. No need to give an example since there is already
one. The number of threads is still limited.

-------------------------------------------------------
Date: Wed 05/14/2003 at 13:16       By: pkm
I will now post an example under #1754

-------------------------------------------------------
Date: Wed 05/14/2003 at 13:04       By: fedemp
As for Bug #1754, I have not been able to get the
same behaviour you describe, but similar crashes in
some platforms. We will look at it, as well as other
problems with threads. If you have more info or even
a trace, it would be very useful for us.


-------------------------------------------------------
Date: Wed 05/14/2003 at 13:03       By: fedemp
As for Bug #1754, I have not been able to get the
same behaviour you describe, but similar crashes in
some platforms. We will look at it, as well as other
problems with threads. If you have more info or even
a trace, it would be very useful for us.


-------------------------------------------------------
Date: Wed 05/14/2003 at 12:59       By: fedemp

The thread is created when start() or detach() is called.
The constructors of the Thread class just initialize
resources.


-------------------------------------------------------
Date: Wed 05/14/2003 at 12:34       By: pkm
[BTW: What about #1754? can nobody reproduce it?]

-------------------------------------------------------
Date: Wed 05/14/2003 at 12:32       By: pkm
When exactly is the thread created? Is is created
when the objects constructor is finished or during
the excecution of start ()? 

-------------------------------------------------------
Date: Wed 05/14/2003 at 11:53       By: fedemp

 Um, yes it seems that the explanation may be a bit confusing.

 Do you agree with replacing:

"by deriving a unique class from the Thread class and by
implementing the Run method."

with

"by instantiating an object of a class derived from the
Thread class. Classes derived from Thread must implement
the method run, which specifies the code of the thread."


-------------------------------------------------------
Date: Sun 04/20/2003 at 13:49       By: pkm
[sorry, did not logged in]


CC List
*******

CC Address                          | Comment
------------------------------------+-----------------------------
bug-commoncpp@gnu.org               | 
peter.karl.mueller@gmx.de           | ()



No files currently attached


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3279&group_id=89



From MAILER-DAEMON Wed May 14 10:03:56 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19FwfP-0005N8-00
	for mharc-bug-commoncpp@gnu.org; Wed, 14 May 2003 09:51:35 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19FuAE-0003JF-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 07:11:14 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19Fu98-0003DO-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 07:10:08 -0400
Received: from subversions.gnu.org ([199.232.41.2])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19Fu2k-0001wS-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 07:03:30 -0400
Received: from www-data by subversions.gnu.org with local (Exim 3.35 #1
	(Debian))	id 19Fu2u-0002ip-00; Wed, 14 May 2003 07:03:40 -0400
To: bug-commoncpp@gnu.org,peter.karl.mueller@gmx.de,fedemp@altern.org
From: nobody@savannah.gnu.org
Message-Id: <E19Fu2u-0002ip-00@subversions.gnu.org>
Date: Wed, 14 May 2003 07:03:40 -0400
X-Mailman-Approved-At: Wed, 14 May 2003 09:51:33 -0400
Subject: [Bug #3279] refman: 8.91 Thread Class Reference:
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 14 May 2003 11:27:41 -0000


=================== BUG #3279: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3279&group_id=89

Changes by: Federico Montesino Pouzols <fedemp@altern.org>
Date: Wed 05/14/03 at 13:03 (Europe/Madrid)

------------------ Additional Follow-up Comments ----------------------------
As for Bug #1754, I have not been able to get the
same behaviour you describe, but similar crashes in
some platforms. We will look at it, as well as other
problems with threads. If you have more info or even
a trace, it would be very useful for us.




=================== BUG #3279: FULL BUG SNAPSHOT ===================


Submitted by: None                    Project: commonc++                    
Submitted on: Sun 04/20/03 at 13:47
Category:  None                       Severity:  5 - Major                  
Bug Group:  None                      Resolution:  None                     
Assigned to:  fedemp                  Status:  Open                         

Summary:  refman: 8.91 Thread Class Reference:

Original Submission:  The reference manual says:

"Every thread of execution in an application is created by
 deriving a unique class from the Thread class and by
 implementing the Run method. base class used to derive all
 threads of execution."

This is IMHO wrong. Since you have at compile time a
fixed number of classes you could only get a fixed number
of threads. This is not the case (or?). AFAICS a thread
is created each time a run method is executed after a
derived class has been instanciated.

Follow-up Comments
*******************

-------------------------------------------------------
Date: Wed 05/14/03 at 13:03         By: fedemp
As for Bug #1754, I have not been able to get the
same behaviour you describe, but similar crashes in
some platforms. We will look at it, as well as other
problems with threads. If you have more info or even
a trace, it would be very useful for us.


-------------------------------------------------------
Date: Wed 05/14/03 at 12:59         By: fedemp

The thread is created when start() or detach() is called.
The constructors of the Thread class just initialize
resources.


-------------------------------------------------------
Date: Wed 05/14/03 at 12:34         By: pkm
[BTW: What about #1754? can nobody reproduce it?]

-------------------------------------------------------
Date: Wed 05/14/03 at 12:32         By: pkm
When exactly is the thread created? Is is created
when the objects constructor is finished or during
the excecution of start ()? 

-------------------------------------------------------
Date: Wed 05/14/03 at 11:53         By: fedemp

 Um, yes it seems that the explanation may be a bit confusing.

 Do you agree with replacing:

"by deriving a unique class from the Thread class and by
implementing the Run method."

with

"by instantiating an object of a class derived from the
Thread class. Classes derived from Thread must implement
the method run, which specifies the code of the thread."


-------------------------------------------------------
Date: Sun 04/20/03 at 13:49         By: pkm
[sorry, did not logged in]


CC List
*******

CC Address                          | Comment
------------------------------------+-----------------------------
bug-commoncpp@gnu.org               | 
peter.karl.mueller@gmx.de           | ()



No files currently attached


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3279&group_id=89



From MAILER-DAEMON Wed May 14 10:05:06 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19FwfP-0005NP-00
	for mharc-bug-commoncpp@gnu.org; Wed, 14 May 2003 09:51:35 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19FuS4-00005I-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 07:29:40 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19FuRB-0008Ld-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 07:28:46 -0400
Received: from subversions.gnu.org ([199.232.41.2])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19FuF5-0004g3-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 07:16:15 -0400
Received: from www-data by subversions.gnu.org with local (Exim 3.35 #1
	(Debian))	id 19FuFD-000365-00; Wed, 14 May 2003 07:16:23 -0400
To: bug-commoncpp@gnu.org,peter.karl.mueller@gmx.de,fedemp@altern.org
From: nobody@savannah.gnu.org
Message-Id: <E19FuFD-000365-00@subversions.gnu.org>
Date: Wed, 14 May 2003 07:16:23 -0400
X-Mailman-Approved-At: Wed, 14 May 2003 09:51:33 -0400
Subject: [Bug #3279] refman: 8.91 Thread Class Reference:
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 14 May 2003 11:33:52 -0000


=================== BUG #3279: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3279&group_id=89

Changes by: Peter Karl Müller <peter.karl.mueller@gmx.de>
Date: Wed 05/14/2003 at 13:16 (Europe/Berlin)

------------------ Additional Follow-up Comments ----------------------------
I will now post an example under #1754



=================== BUG #3279: FULL BUG SNAPSHOT ===================


Submitted by: None                    Project: commonc++                    
Submitted on: Sun 04/20/2003 at 13:47
Category:  None                       Severity:  5 - Major                  
Bug Group:  None                      Resolution:  None                     
Assigned to:  fedemp                  Status:  Open                         

Summary:  refman: 8.91 Thread Class Reference:

Original Submission:  The reference manual says:

"Every thread of execution in an application is created by
 deriving a unique class from the Thread class and by
 implementing the Run method. base class used to derive all
 threads of execution."

This is IMHO wrong. Since you have at compile time a
fixed number of classes you could only get a fixed number
of threads. This is not the case (or?). AFAICS a thread
is created each time a run method is executed after a
derived class has been instanciated.

Follow-up Comments
*******************

-------------------------------------------------------
Date: Wed 05/14/2003 at 13:16       By: pkm
I will now post an example under #1754

-------------------------------------------------------
Date: Wed 05/14/2003 at 13:04       By: fedemp
As for Bug #1754, I have not been able to get the
same behaviour you describe, but similar crashes in
some platforms. We will look at it, as well as other
problems with threads. If you have more info or even
a trace, it would be very useful for us.


-------------------------------------------------------
Date: Wed 05/14/2003 at 13:03       By: fedemp
As for Bug #1754, I have not been able to get the
same behaviour you describe, but similar crashes in
some platforms. We will look at it, as well as other
problems with threads. If you have more info or even
a trace, it would be very useful for us.


-------------------------------------------------------
Date: Wed 05/14/2003 at 12:59       By: fedemp

The thread is created when start() or detach() is called.
The constructors of the Thread class just initialize
resources.


-------------------------------------------------------
Date: Wed 05/14/2003 at 12:34       By: pkm
[BTW: What about #1754? can nobody reproduce it?]

-------------------------------------------------------
Date: Wed 05/14/2003 at 12:32       By: pkm
When exactly is the thread created? Is is created
when the objects constructor is finished or during
the excecution of start ()? 

-------------------------------------------------------
Date: Wed 05/14/2003 at 11:53       By: fedemp

 Um, yes it seems that the explanation may be a bit confusing.

 Do you agree with replacing:

"by deriving a unique class from the Thread class and by
implementing the Run method."

with

"by instantiating an object of a class derived from the
Thread class. Classes derived from Thread must implement
the method run, which specifies the code of the thread."


-------------------------------------------------------
Date: Sun 04/20/2003 at 13:49       By: pkm
[sorry, did not logged in]


CC List
*******

CC Address                          | Comment
------------------------------------+-----------------------------
bug-commoncpp@gnu.org               | 
peter.karl.mueller@gmx.de           | ()



No files currently attached


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3279&group_id=89



From MAILER-DAEMON Wed May 14 10:19:28 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19Fx6O-0004bh-00
	for mharc-bug-commoncpp@gnu.org; Wed, 14 May 2003 10:19:28 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19Fx6L-0004bJ-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 10:19:25 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19Fx6I-0004aM-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 10:19:24 -0400
Received: from acate.com.br ([200.215.17.89] helo=cli004.brasmap)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19Fx28-0003hi-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 10:15:04 -0400
Received: from cli004.brasmap (localhost.localdomain [127.0.0.1])
	by cli004.brasmap (Postfix) with SMTP id E593B5B663
	for <bug-commoncpp@gnu.org>; Wed, 14 May 2003 11:14:47 -0300 (BRT)
Date: Wed, 14 May 2003 11:14:42 -0300
From: Marcelo Dalmas <mad@brasmap.com.br>
To: bug-commoncpp@gnu.org
Message-Id: <20030514111442.5abaff73.mad@brasmap.com.br>
In-Reply-To: <E19Eqen-00020U-00@subversions.gnu.org>
References: <E19Eqen-00020U-00@subversions.gnu.org>
Organization: BRASMAP Siatemas, Consultoria e =?ISO-8859-1?Q?Com=E9rcio?=
 LTDA.
X-Mailer: Sylpheed version 0.8.11 (GTK+ 1.2.10; i586-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: multipart/signed; protocol="application/pgp-signature";
 micalg="pgp-sha1"; boundary="wFvk4D7LWM6cg:=."
Subject: Re: [Bug #3289] Function missing, v2 1.0.9, Datetime::Datetime(
 time_t tm )
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 14 May 2003 14:19:26 -0000

--wFvk4D7LWM6cg:=.
Content-Type: multipart/mixed;
 boundary="Multipart_Wed__14_May_2003_11:14:42_-0300_082040b0"


--Multipart_Wed__14_May_2003_11:14:42_-0300_082040b0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

In attachment Datetime::Datetime( time_t tm ).

Hope this helps,

On Sun, 11 May 2003 09:14:25 -0400
nobody@savannah.gnu.org wrote:

>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D BUG #3289: LATE=
ST MODIFICATIONS =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> http://savannah.gnu.org/bugs/?func=3Ddetailbug&bug_id=3D3289&group_id=3D89
>=20
> Changes by: Federico Montesino Pouzols <fedemp@altern.org>
> Date: Sun 05/11/2003 at 15:14 (Europe/Madrid)
>=20
>             What     | Removed                   | Added
> -------------------------------------------------------------------------=
--
>           Resolution | None                      | Later
>          Assigned to | None                      | fedemp
>                   CC |                           | bug-commoncpp@gnu.org
>=20
>=20
> ------------------ Additional Follow-up Comments ------------------------=
----
>=20
>  Is this method missing for any particular reason I am not
> able to see, or it simply was forgotten? In the latter case,
> its implementation should be as simple as the implementation
> of the constructor without parameters.
>=20
>=20
>=20
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D BUG #3289: FULL=
 BUG SNAPSHOT =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>=20
>=20
> Submitted by: drzoom                  Project: commonc++                 =
  =20
> Submitted on: Mon 04/21/2003 at 14:42
> Category:  None                       Severity:  5 - Major               =
  =20
> Bug Group:  None                      Resolution:  Later                 =
  =20
> Assigned to:  fedemp                  Status:  Open                      =
  =20
>=20
> Summary:  Function missing, v2 1.0.9, Datetime::Datetime( time_t tm )
>=20
> Original Submission:  This Function is currently missing, but declared in=
 the header.
>=20
> Follow-up Comments
> *******************
>=20
> -------------------------------------------------------
> Date: Sun 05/11/2003 at 15:14       By: fedemp
>=20
>  Is this method missing for any particular reason I am not
> able to see, or it simply was forgotten? In the latter case,
> its implementation should be as simple as the implementation
> of the constructor without parameters.
>=20
>=20
> CC List
> *******
>=20
> CC Address                          | Comment
> ------------------------------------+-----------------------------
> bug-commoncpp@gnu.org               |=20
>=20
>=20
>=20
> No files currently attached
>=20
>=20
> For detailed info, follow this link:
> http://savannah.gnu.org/bugs/?func=3Ddetailbug&bug_id=3D3289&group_id=3D89
>=20
>=20
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp


--=20
-------------------------------------------------
  Marcelo Dalmas - Eng. de Controle e Automa=E7=E3o
-------------------------------------------------
  BRASMAP Sistemas, Consultoria e Com=E9rcio Ltda.
        Engenharia em Aquisi=E7=E3o de Dados

     www.brasmap.com.br - info@brasmap.com.br
Fone: (48) 333-2218 ramal 2114 Fax: (48) 333-3745
-------------------------------------------------


--Multipart_Wed__14_May_2003_11:14:42_-0300_082040b0
Content-Type: application/octet-stream;
 name="datetime-20030514.patch"
Content-Disposition: attachment;
 filename="datetime-20030514.patch"
Content-Transfer-Encoding: base64

SW5kZXg6IHNyYy9kYXRlLmNwcAo9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09ClJDUyBmaWxlOiAvdXNyL2xvY2FsL2N2c3Jv
b3QvYnJhc21hcC9jb21tb25jcHAyL3NyYy9kYXRlLmNwcCx2CnJldHJpZXZpbmcgcmV2aXNpb24g
MS4xNQpkaWZmIC11IC1yMS4xNSBkYXRlLmNwcAotLS0gc3JjL2RhdGUuY3BwCTIwMDMvMDUvMTQg
MTI6NTg6MDAJMS4xNQorKysgc3JjL2RhdGUuY3BwCTIwMDMvMDUvMTQgMTM6MDE6MzcKQEAgLTY4
Nyw2ICs2ODcsMTIgQEAKIAlyZXR1cm4gdDsKIH0KIAorRGF0ZXRpbWU6OkRhdGV0aW1lKHRpbWVf
dCB0bSkKK3sKKwlzdHJ1Y3QgdG0gKmR0ID0gbG9jYWx0aW1lKCZ0bSk7CisJdG9KdWxpYW4oZHQt
PnRtX3llYXIgKyAxOTAwLCBkdC0+dG1fbW9uICsgMSwgZHQtPnRtX21kYXkpOworCXRvU2Vjb25k
cyhkdC0+dG1faG91ciwgZHQtPnRtX21pbiwgZHQtPnRtX3NlYyk7Cit9CiAKIERhdGV0aW1lOjpE
YXRldGltZSh0bSAqZHQpIDoKIERhdGUoZHQpLCBUaW1lKGR0KQo=

--Multipart_Wed__14_May_2003_11:14:42_-0300_082040b0--

--wFvk4D7LWM6cg:=.
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE+wk9X95NRejZp8BwRAt25AJ9x/Ae4VK7tRvnquLiwSjlc6XfLQACeLGzk
vADHHXgUF3FldRSXGYNP0Ks=
=69wx
-----END PGP SIGNATURE-----

--wFvk4D7LWM6cg:=.--



From MAILER-DAEMON Wed May 14 10:31:25 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19FwfQ-0005NS-00
	for mharc-bug-commoncpp@gnu.org; Wed, 14 May 2003 09:51:36 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19FuWb-00026e-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 07:34:21 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19FuW2-0001uE-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 07:33:47 -0400
Received: from subversions.gnu.org ([199.232.41.2])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19FtYr-00052a-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 06:32:37 -0400
Received: from www-data by subversions.gnu.org with local (Exim 3.35 #1
	(Debian))	id 19FtZ0-0001nR-00; Wed, 14 May 2003 06:32:46 -0400
To: bug-commoncpp@gnu.org,peter.karl.mueller@gmx.de,fedemp@altern.org
From: nobody@savannah.gnu.org
Message-Id: <E19FtZ0-0001nR-00@subversions.gnu.org>
Date: Wed, 14 May 2003 06:32:46 -0400
X-Mailman-Approved-At: Wed, 14 May 2003 09:51:33 -0400
Subject: [Bug #3279] refman: 8.91 Thread Class Reference:
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 14 May 2003 11:37:30 -0000


=================== BUG #3279: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3279&group_id=89

Changes by: Peter Karl Müller <peter.karl.mueller@gmx.de>
Date: Wed 05/14/2003 at 12:32 (Europe/Berlin)

------------------ Additional Follow-up Comments ----------------------------
When exactly is the thread created? Is is created
when the objects constructor is finished or during
the excecution of start ()? 



=================== BUG #3279: FULL BUG SNAPSHOT ===================


Submitted by: None                    Project: commonc++                    
Submitted on: Sun 04/20/2003 at 13:47
Category:  None                       Severity:  5 - Major                  
Bug Group:  None                      Resolution:  None                     
Assigned to:  None                    Status:  Open                         

Summary:  refman: 8.91 Thread Class Reference:

Original Submission:  The reference manual says:

"Every thread of execution in an application is created by
 deriving a unique class from the Thread class and by
 implementing the Run method. base class used to derive all
 threads of execution."

This is IMHO wrong. Since you have at compile time a
fixed number of classes you could only get a fixed number
of threads. This is not the case (or?). AFAICS a thread
is created each time a run method is executed after a
derived class has been instanciated.

Follow-up Comments
*******************

-------------------------------------------------------
Date: Wed 05/14/2003 at 12:32       By: pkm
When exactly is the thread created? Is is created
when the objects constructor is finished or during
the excecution of start ()? 

-------------------------------------------------------
Date: Wed 05/14/2003 at 11:53       By: fedemp

 Um, yes it seems that the explanation may be a bit confusing.

 Do you agree with replacing:

"by deriving a unique class from the Thread class and by
implementing the Run method."

with

"by instantiating an object of a class derived from the
Thread class. Classes derived from Thread must implement
the method run, which specifies the code of the thread."


-------------------------------------------------------
Date: Sun 04/20/2003 at 13:49       By: pkm
[sorry, did not logged in]


CC List
*******

CC Address                          | Comment
------------------------------------+-----------------------------
bug-commoncpp@gnu.org               | 
peter.karl.mueller@gmx.de           | ()



No files currently attached


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3279&group_id=89



From MAILER-DAEMON Wed May 14 10:37:56 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19FxHl-0000jm-00
	for mharc-bug-commoncpp@gnu.org; Wed, 14 May 2003 10:31:13 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19FxEd-0007e4-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 10:27:59 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19Fwrx-0000sJ-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 10:04:36 -0400
Received: from pool-138-89-45-96.mad.east.verizon.net ([138.89.45.96]
	helo=home.bayonne.dyndns.org)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 19Fwrv-0000qV-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 10:04:31 -0400
Received: from 192.168.1.104 ([192.168.1.104])
	by home.bayonne.dyndns.org (8.11.6/8.11.6) with ESMTP id h4EEspF01593;
	Wed, 14 May 2003 10:54:51 -0400
From: David Sugar <dyfet@ostel.com>
To: Federico Montesino Pouzols <fedemp@altern.org>
Date: Wed, 14 May 2003 09:56:05 -0400
User-Agent: KMail/1.5
References: <Pine.LNX.4.44.0304231828202.1218-100000@MainServer.bksys.co.in>
	<3EC229E9.2070407@ostel.com> <20030514115211.GE5529@bulbasaur.rediris.es>
In-Reply-To: <20030514115211.GE5529@bulbasaur.rediris.es>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200305140956.05087.dyfet@ostel.com>
cc: bug-commoncpp@gnu.org
Subject: Re: [Ccrtp-devel] Compile error - ccrtp 1.0.0
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 14 May 2003 14:31:12 -0000

Yes, this is an odd one...I saw the example used involved creating, sleeping, 
and deleting threads in series.  However, the "run" method in the example 
sleeps for 1 millisecond, while the delete method waits in increments of 10 
milli seconds.  So I suspect the thread has already exited into final when 
delete is called.  My suggestion is to retest this with the run method having 
an infinite sleep (sleep (~0)), and the method that starts it off sleep a 
short while and then hit delete.  Thereby delete occurs while still in the 
"run" loop.

I'm going by the example given, with:

	TestThread()
	{};

	void run()
	{
	    sleep(1);
	}

and 
		while ( tt->isRunning() ) ost::Thread::sleep(10);
		delete tt;

So he deliberately tries to wait for the thread to exit before joining.  Yes, 
this may indeed be broke since at least some releases of LinuxThread do not 
properly support join (pthread_join) on threads that heave already exited (it 
leaves a 4m virtual page mapped).


On Wednesday 14 May 2003 07:52 am, Federico Montesino Pouzols wrote:
> There is possibly a bug that limits the number of creatable
> threads, though it does not occur on all platforms. It has been
> reported through the bug tracking system of Savannah.
>
> On Wed, May 14, 2003 at 07:35:05AM -0400, David Sugar wrote:
> > In fact, I would like to see 1.0.10 out by the end of the week.  I think
> > the pending issues I was working on related to builds are now closed.
> > There is still a strange problem with redhat and nptl related soley to
> > suspend and resume, but it's not a fatel flaw since all my regular apps
> > build and run.  In fact rh9 is broken since nptl is only fully
> > compatible with kernel late 2.5 kernels (or 2.6), and they still have
> > 2.4 which doesn't fully support it.  But that's another story...
> >
> > I saw we had some new bugs filter through, the most interesting being a
> > memory leak in stringtokenizer.  I think that the win32 thread
> > destructor should delete priv.  Other than that, what else is left?
> >
> > Federico Montesino Pouzols wrote:
> > >	Let's move this issue to bug-commoncpp...
> > >
> > >	I like this idea. Should we release 1.0.10 once we fix the
> > >bugs that are pending, and then go to 1.1.0 (with the new socketport
> > >stuff)?
> > >
> > >On Thu, Apr 24, 2003 at 07:57:31AM -0400, David Sugar wrote:
> > >>Done.
> > >>
> > >>I also have a new and better idea for handling of the socketport
> > >>constructor change (and the other recent 1.0.x changes related to
> > >>macosx).  Let's make the next release from the "RELEASE1" tree 1.1.0
> > >> with the socketport changes, and move "HEAD" into a future "1.9" or
> > >> similar release...This gives a clear delination in release for
> > >> something that will change backward compatibility.
> > >
> > >_______________________________________________
> > >Bug-commoncpp mailing list
> > >Bug-commoncpp@gnu.org
> > >http://mail.gnu.org/mailman/listinfo/bug-commoncpp
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp




From MAILER-DAEMON Wed May 14 10:55:28 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19FxfD-0000Ku-00
	for mharc-bug-commoncpp@gnu.org; Wed, 14 May 2003 10:55:27 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19FxfA-0000KI-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 10:55:24 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19Fxf9-0000K3-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 10:55:24 -0400
Received: from subversions.gnu.org ([199.232.41.2])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19Fxf9-0000Jx-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 10:55:23 -0400
Received: from www-data by subversions.gnu.org with local (Exim 3.35 #1
	(Debian))	id 19FxfH-0004DI-00; Wed, 14 May 2003 10:55:31 -0400
To: bug-commoncpp@gnu.org,savannah.email@tracker.drzoom.ch,fedemp@altern.org
From: nobody@savannah.gnu.org
Message-Id: <E19FxfH-0004DI-00@subversions.gnu.org>
Date: Wed, 14 May 2003 10:55:31 -0400
Subject: [Bug #3289] Function missing, v2 1.0.9, Datetime::Datetime( time_t tm
	)
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 14 May 2003 14:55:25 -0000


=================== BUG #3289: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3289&group_id=89

Changes by: Federico Montesino Pouzols <fedemp@altern.org>
Date: Wed 05/14/03 at 16:55 (Europe/Madrid)

            What     | Removed                   | Added
---------------------------------------------------------------------------
          Resolution | Later                     | Fixed
              Status | Open                      | Closed


------------------ Additional Follow-up Comments ----------------------------
It is now fixed in CVS.




=================== BUG #3289: FULL BUG SNAPSHOT ===================


Submitted by: drzoom                  Project: commonc++                    
Submitted on: Mon 04/21/03 at 14:42
Category:  None                       Severity:  5 - Major                  
Bug Group:  None                      Resolution:  Fixed                    
Assigned to:  fedemp                  Status:  Closed                       

Summary:  Function missing, v2 1.0.9, Datetime::Datetime( time_t tm )

Original Submission:  This Function is currently missing, but declared in the header.

Follow-up Comments
*******************

-------------------------------------------------------
Date: Wed 05/14/03 at 16:55         By: fedemp
It is now fixed in CVS.


-------------------------------------------------------
Date: Sun 05/11/03 at 15:14         By: fedemp

 Is this method missing for any particular reason I am not
able to see, or it simply was forgotten? In the latter case,
its implementation should be as simple as the implementation
of the constructor without parameters.


CC List
*******

CC Address                          | Comment
------------------------------------+-----------------------------
bug-commoncpp@gnu.org               | 



No files currently attached


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3289&group_id=89



From MAILER-DAEMON Wed May 14 11:18:04 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19Fy15-0001Kq-00
	for mharc-bug-commoncpp@gnu.org; Wed, 14 May 2003 11:18:03 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19Fy13-0001J7-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 11:18:01 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19FxxP-0008C3-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 11:14:16 -0400
Received: from subversions.gnu.org ([199.232.41.2])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19Fxn5-0003aF-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 11:03:35 -0400
Received: from www-data by subversions.gnu.org with local (Exim 3.35 #1
	(Debian))	id 19FxnF-0004Sm-00; Wed, 14 May 2003 11:03:45 -0400
To: bug-commoncpp@gnu.org,peter.karl.mueller@gmx.de,fedemp@altern.org
From: nobody@savannah.gnu.org
Message-Id: <E19FxnF-0004Sm-00@subversions.gnu.org>
Date: Wed, 14 May 2003 11:03:45 -0400
Subject: [Bug #3279] refman: 8.91 Thread Class Reference:
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 14 May 2003 15:18:02 -0000


=================== BUG #3279: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3279&group_id=89

Changes by: Federico Montesino Pouzols <fedemp@altern.org>
Date: Wed 05/14/03 at 17:03 (Europe/Madrid)

            What     | Removed                   | Added
---------------------------------------------------------------------------
          Resolution | None                      | Fixed
              Status | Open                      | Closed


------------------ Additional Follow-up Comments ----------------------------
The doc clarification is in CVS, and dyfet is addressing the
threads related bug.




=================== BUG #3279: FULL BUG SNAPSHOT ===================


Submitted by: None                    Project: commonc++                    
Submitted on: Sun 04/20/03 at 13:47
Category:  None                       Severity:  5 - Major                  
Bug Group:  None                      Resolution:  Fixed                    
Assigned to:  fedemp                  Status:  Closed                       

Summary:  refman: 8.91 Thread Class Reference:

Original Submission:  The reference manual says:

"Every thread of execution in an application is created by
 deriving a unique class from the Thread class and by
 implementing the Run method. base class used to derive all
 threads of execution."

This is IMHO wrong. Since you have at compile time a
fixed number of classes you could only get a fixed number
of threads. This is not the case (or?). AFAICS a thread
is created each time a run method is executed after a
derived class has been instanciated.

Follow-up Comments
*******************

-------------------------------------------------------
Date: Wed 05/14/03 at 17:03         By: fedemp
The doc clarification is in CVS, and dyfet is addressing the
threads related bug.


-------------------------------------------------------
Date: Wed 05/14/03 at 13:23         By: pkm
Sorry. No need to give an example since there is already
one. The number of threads is still limited.

-------------------------------------------------------
Date: Wed 05/14/03 at 13:16         By: pkm
I will now post an example under #1754

-------------------------------------------------------
Date: Wed 05/14/03 at 13:04         By: fedemp
As for Bug #1754, I have not been able to get the
same behaviour you describe, but similar crashes in
some platforms. We will look at it, as well as other
problems with threads. If you have more info or even
a trace, it would be very useful for us.


-------------------------------------------------------
Date: Wed 05/14/03 at 13:03         By: fedemp
As for Bug #1754, I have not been able to get the
same behaviour you describe, but similar crashes in
some platforms. We will look at it, as well as other
problems with threads. If you have more info or even
a trace, it would be very useful for us.


-------------------------------------------------------
Date: Wed 05/14/03 at 12:59         By: fedemp

The thread is created when start() or detach() is called.
The constructors of the Thread class just initialize
resources.


-------------------------------------------------------
Date: Wed 05/14/03 at 12:34         By: pkm
[BTW: What about #1754? can nobody reproduce it?]

-------------------------------------------------------
Date: Wed 05/14/03 at 12:32         By: pkm
When exactly is the thread created? Is is created
when the objects constructor is finished or during
the excecution of start ()? 

-------------------------------------------------------
Date: Wed 05/14/03 at 11:53         By: fedemp

 Um, yes it seems that the explanation may be a bit confusing.

 Do you agree with replacing:

"by deriving a unique class from the Thread class and by
implementing the Run method."

with

"by instantiating an object of a class derived from the
Thread class. Classes derived from Thread must implement
the method run, which specifies the code of the thread."


-------------------------------------------------------
Date: Sun 04/20/03 at 13:49         By: pkm
[sorry, did not logged in]


CC List
*******

CC Address                          | Comment
------------------------------------+-----------------------------
bug-commoncpp@gnu.org               | 
peter.karl.mueller@gmx.de           | ()



No files currently attached


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3279&group_id=89



From MAILER-DAEMON Wed May 14 11:29:52 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19FxlH-00031M-00
	for mharc-bug-commoncpp@gnu.org; Wed, 14 May 2003 11:01:43 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19FxhZ-0001Ow-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 10:57:53 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19Fxfl-0000RW-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 10:56:02 -0400
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19FxeN-0000F2-00
	for bug-commoncpp@gnu.org; Wed, 14 May 2003 10:54:36 -0400
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 19Fxl2-0004x8-00; Wed, 14 May 2003 17:01:28 +0200
Date: Wed, 14 May 2003 17:01:28 +0200
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Marcelo Dalmas <mad@brasmap.com.br>
Message-ID: <20030514150128.GF5529@bulbasaur.rediris.es>
Mail-Followup-To: Marcelo Dalmas <mad@brasmap.com.br>,
	bug-commoncpp@gnu.org
References: <E19Eqen-00020U-00@subversions.gnu.org>
	<20030514111442.5abaff73.mad@brasmap.com.br>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030514111442.5abaff73.mad@brasmap.com.br>
User-Agent: Mutt/1.5.4i
Sender: Federico Montesino Pouzols <fedemp@altern.org>
cc: bug-commoncpp@gnu.org
Subject: 
 Re: [Bug #3289] Function missing, v2 1.0.9, Datetime::Datetime( time_t tm )
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Wed, 14 May 2003 15:01:42 -0000


	Sure it helps, it is in CVS.

On Wed, May 14, 2003 at 11:14:42AM -0300, Marcelo Dalmas wrote:
> In attachment Datetime::Datetime( time_t tm ).
> 
> Hope this helps,
> 



From MAILER-DAEMON Thu May 15 07:38:30 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19GH3y-0005KT-00
	for mharc-bug-commoncpp@gnu.org; Thu, 15 May 2003 07:38:18 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19GGw8-00027C-00
	for bug-commoncpp@gnu.org; Thu, 15 May 2003 07:30:12 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19GGuw-0001Lk-00
	for bug-commoncpp@gnu.org; Thu, 15 May 2003 07:29:00 -0400
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19GGuT-0000yw-00
	for bug-commoncpp@gnu.org; Thu, 15 May 2003 07:28:30 -0400
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 19GH1D-0006dM-00; Thu, 15 May 2003 13:35:27 +0200
Date: Thu, 15 May 2003 13:35:27 +0200
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Liviu <liviu@netonwave.com>
Message-ID: <20030515113527.GA25441@bulbasaur.rediris.es>
Mail-Followup-To: Liviu <liviu@netonwave.com>, bug-commoncpp@gnu.org
References: <1547026763.20030424173632@netonwave.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1547026763.20030424173632@netonwave.com>
User-Agent: Mutt/1.5.4i
Sender: Federico Montesino Pouzols <fedemp@altern.org>
cc: bug-commoncpp@gnu.org
Subject: Re: tcpstream::open thrown exceptions
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 15 May 2003 11:38:17 -0000


	if tcpserver inherits publicly from tcpstream, you can use the
isConnected() call inherited from Socket to know if the socket is
connected. 

On Thu, Apr 24, 2003 at 05:36:32PM +0200, Liviu wrote:
> Hello,
> 
> I'am trying to write a simple client that connects to a telnet server
> using the tcpstream class.
> My code goes like this:
> 
> tcpserver tcp;
> try {
>     tcp.open("127.0.0.1:23");
> }
> catch(Socket* socket)
> {
>     cerr << "An exception was thrown." << endl;
> }
> 
> If the telnet server is running everything goes ok.
> It the telnet server is NOT RUNNING (so the open should fail) the open
> function doesn't throw any exception.
> 
> My question is: How do I know if my client connected or not to the
> server ???
> 
> 
>     
> 
> 
>   
> 
> -- 
> Best regards,
>  Liviu                          mailto:liviu@netonwave.com
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From MAILER-DAEMON Thu May 15 08:07:57 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19GHWe-0001gU-00
	for mharc-bug-commoncpp@gnu.org; Thu, 15 May 2003 08:07:56 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19GHWc-0001cx-00
	for bug-commoncpp@gnu.org; Thu, 15 May 2003 08:07:54 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19GHVf-00011P-00
	for bug-commoncpp@gnu.org; Thu, 15 May 2003 08:06:55 -0400
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19GHUl-0000pp-00
	for bug-commoncpp@gnu.org; Thu, 15 May 2003 08:05:59 -0400
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 19GHbU-0007rV-00; Thu, 15 May 2003 14:12:56 +0200
Date: Thu, 15 May 2003 14:12:56 +0200
From: Federico Montesino Pouzols <fedemp@altern.org>
To: =?iso-8859-1?Q?=C9tienne?= Dupuis <e.dupuis@ateme.fr>
Message-ID: <20030515121256.GB25441@bulbasaur.rediris.es>
Mail-Followup-To: =?iso-8859-1?Q?=C9tienne?= Dupuis <e.dupuis@ateme.fr>,
	bug-commoncpp@gnu.org,
	=?iso-8859-1?Q?Isma=EBl?= Djima <i.djima@ateme.fr>
References: <002b01c3147a$276e94f0$b71010ac@pc183>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <002b01c3147a$276e94f0$b71010ac@pc183>
User-Agent: Mutt/1.5.4i
Sender: Federico Montesino Pouzols <fedemp@altern.org>
cc: bug-commoncpp@gnu.org
cc: =?iso-8859-1?Q?Isma=EBl?= Djima <i.djima@ateme.fr>
Subject: Re: Thread.join() ?
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 15 May 2003 12:07:55 -0000


	I have just tested you example with the code in CVS and it
works fine. It may be an issue with your glibc or your kernel, as join
is a recent addition and I had not ever seen it failing. Also, the
strange behaviour of yield suggest that there is something very weird
in you system.

On Wed, May 07, 2003 at 11:22:17AM +0200, Étienne Dupuis wrote:
> Greetings,
> 
> Method Thread.join() seems to never return. On Linux, with Common C++ 1.0.9, consider the following program :
> 
> int main()
> {
>     class Wait : public Thread {
>         protected :
>             virtual void run() {
>                 sleep(1000);
>             }
>     };
> 
>     Wait wait;
>     wait.start();
>     wait.join();
> 
>     return 0;
> }
> 
> It never ends as it is stuck in the join() method. However, on Windows 2000 it works correctly. Moreover, method Thread::yield() yields as much as one second (!) on my Linux machine but works as expected on Windows.
> 
> Anyone got similar problems ? Should I consider that my Linux kernel is the culprit ? Kernel version is 2.4.18-14.
> 
> Thanks, Étienne Dupuis

> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp




From MAILER-DAEMON Thu May 15 08:40:01 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19GI1I-0001Lf-00
	for mharc-bug-commoncpp@gnu.org; Thu, 15 May 2003 08:39:36 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19GI0l-00008o-00
	for bug-commoncpp@gnu.org; Thu, 15 May 2003 08:39:03 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19GHzh-0006gA-00
	for bug-commoncpp@gnu.org; Thu, 15 May 2003 08:38:00 -0400
Received: from bulbasaur.rediris.es ([130.206.194.34])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19GHzg-0006c9-00
	for bug-commoncpp@gnu.org; Thu, 15 May 2003 08:37:56 -0400
Received: from fedemp by bulbasaur.rediris.es with local (Exim 3.36 #1
	(Debian))	id 19GI6R-0007sI-00; Thu, 15 May 2003 14:44:55 +0200
Date: Thu, 15 May 2003 14:44:55 +0200
From: Federico Montesino Pouzols <fedemp@altern.org>
To: Mike Suchoff <mikes@in-tune.com>
Message-ID: <20030515124455.GC25441@bulbasaur.rediris.es>
Mail-Followup-To: Mike Suchoff <mikes@in-tune.com>, bug-commoncpp@gnu.org
References: <LLEGJHOMPFHINGBACKKLGEEPCJAA.mikes@in-tune.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <LLEGJHOMPFHINGBACKKLGEEPCJAA.mikes@in-tune.com>
User-Agent: Mutt/1.5.4i
Sender: Federico Montesino Pouzols <fedemp@altern.org>
cc: bug-commoncpp@gnu.org
Subject: Re: TimerPort return values
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: Federico Montesino Pouzols <fedemp@altern.org>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 15 May 2003 12:39:34 -0000


	Ok, it is fixed in CVS.

On Mon, Mar 31, 2003 at 07:57:00AM -0500, Mike Suchoff wrote:
> TimerPort::getTimer() and TimerPort::getElapsed() are documented as
> return -1 when timer is inactive.
> However these routines return a timeout_t which is defined as an unsigned
> long.
> 
> I believe these routines should be documented as returning the value
> TIMEOUT_INF when the timer is inactive.  That is, it returns the largest
> unsigned 32 bit integer (all 1's).
> 
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp



From MAILER-DAEMON Fri May 16 07:35:01 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19GdH5-0007MD-00
	for mharc-bug-commoncpp@gnu.org; Fri, 16 May 2003 07:21:19 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19GdCC-0005f0-00
	for bug-commoncpp@gnu.org; Fri, 16 May 2003 07:16:16 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19Gd4q-0004C5-00
	for bug-commoncpp@gnu.org; Fri, 16 May 2003 07:08:40 -0400
Received: from subversions.gnu.org ([199.232.41.2])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19Gd1v-0003tP-00
	for bug-commoncpp@gnu.org; Fri, 16 May 2003 07:05:39 -0400
Received: from www-data by subversions.gnu.org with local (Exim 4.20)
	id 19Gd20-000163-Kk; Fri, 16 May 2003 07:05:44 -0400
To: bug-commoncpp@gnu.org,awagger@web.de,fedemp@altern.org
From: nobody@savannah.gnu.org
X-Savannah-Project: commoncpp
X-Savannah-Artifact: bug
X-Savannah-Artifact-ID: 3315
Message-Id: <E19Gd20-000163-Kk@subversions.gnu.org>
Sender: www-data <www-data@subversions.gnu.org>
Date: Fri, 16 May 2003 07:05:44 -0400
Subject: [Bug #3315] problems with ftp code in Borland C++ Builder
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 16 May 2003 11:21:17 -0000



=================== BUG #3315: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3315&group_id=89

Changes by: Axel Waggershauser <awagger@web.de>
Date: Fri 05/16/2003 at 11:05 (GMT)

------------------ Additional Follow-up Comments ----------------------------
I still don't know where exactly the problem number 1) comes from, but a fix that does not break the lib on any other platform but still fixes the issue with the BCB is of course:

#ifndef __BORLANDC__
    str.get(); // skip space
#endif /* __BORLANDC__ */



=================== BUG #3315: FULL BUG SNAPSHOT ===================


Submitted by: awagger                 Project: commonc++                    
Submitted on: Wed 04/23/2003 at 22:36
Category:  None                       Severity:  5 - Major                  
Bug Group:  None                      Resolution:  Later                    
Assigned to:  fedemp                  Status:  Open                         

Summary:  problems with ftp code in Borland C++ Builder

Original Submission:  I found (and fixed) two problems with the ftp code in libcommonc++2-1.0.9 when using the Borland C++ Builder (version 5).

1) I had to comment out line ftp.cpp:647 in method FTPSocket::DirEntry::parse(string li):

    str.get();  // skip space

since the mentioned space seemed to be included in the variable "junk", filled in the line bevore (ftp.cpp:646):

    str >> access >> junk >> user >> group >> size >> junk >> junk >> junk;


I don't know if it is an istream operator implementation problem or a unix <-> windows problem.


2) I had to change line ftp.cpp:482:

    ofstream f( lfilename.c_str() );

by explicitly specifying binary output mode like this:

    ofstream f( lfilename.c_str(),
        std::ios::out|std::ios::trunc|std::ios::binary );

otherwise the char '\n' got written as two bytes (as usual in windows in text-mode). So this is clearly a unix <-> windows porting problem. But I think, it should be perfectly ok, to use the same code for unix, since the result should be the same.



Follow-up Comments
*******************

-------------------------------------------------------
Date: Fri 05/16/2003 at 11:05       By: awagger
I still don't know where exactly the problem number 1) comes from, but a fix that does not break the lib on any other platform but still fixes the issue with the BCB is of course:

#ifndef __BORLANDC__
    str.get(); // skip space
#endif /* __BORLANDC__ */

-------------------------------------------------------
Date: Sun 05/11/2003 at 13:02       By: fedemp

 The second issue is fixed in CVS. As for the first one, I
suspect that your proposed change will break the library on
other platforms. Does anyone know if this happens because of
the istream implementation of Borland c++?.



CC List
*******

CC Address                          | Comment
------------------------------------+-----------------------------
bug-commoncpp@gnu.org               | 



No files currently attached


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3315&group_id=89



From MAILER-DAEMON Fri May 16 09:14:19 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19Geqs-0004JX-00
	for mharc-bug-commoncpp@gnu.org; Fri, 16 May 2003 09:02:22 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19Ge3i-0001oJ-00
	for bug-commoncpp@gnu.org; Fri, 16 May 2003 08:11:34 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19Gdxc-0007gY-00
	for bug-commoncpp@gnu.org; Fri, 16 May 2003 08:05:17 -0400
Received: from [195.39.239.140] (helo=obiwan.sturmlan.net)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19Gdix-0000zF-00
	for bug-commoncpp@gnu.org; Fri, 16 May 2003 07:50:07 -0400
Received: from cerberos.wg (pD9E38609.dip.t-dialin.net [217.227.134.9])
	(authenticated)
	by obiwan.sturmlan.net (8.11.6/8.11.6) with ESMTP id h4GBpDn06293
	for <bug-commoncpp@gnu.org>; Fri, 16 May 2003 13:51:14 +0200
Received: from strand.wg
	([192.168.1.2] helo=strand ident=axel)
	by cerberos.wg with esmtp (Exim 3.35 #1 (Debian))
	id 19Gdij-0002iM-00
	for <bug-commoncpp@gnu.org>; Fri, 16 May 2003 13:49:53 +0200
From: Axel Waggershauser <awagger@web.de>
To: bug-commoncpp@gnu.org
Content-Type: text/plain
Organization: 
Message-Id: <1053085793.895.34.camel@strand>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.3 
Date: 16 May 2003 13:49:53 +0200
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Fri, 16 May 2003 09:02:17 -0400
Subject: put typedefs in config.h into namespace ost?
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 16 May 2003 12:11:40 -0000

Hi,

I have a problem using libcommonc++ together with libtiff, since both
typedef the same types (int16, int32, etc.). My workaround is to put
these typedefs in config.h into the namespace ost.

Would it be possible to adopt this fix to the library, so I don't have
to patch it everytime, or does anybody know of a better solution?

Thanks, Axel.




From MAILER-DAEMON Fri May 16 09:14:29 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19Geqs-0004JW-00
	for mharc-bug-commoncpp@gnu.org; Fri, 16 May 2003 09:02:22 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19GIQy-0005wg-00
	for bug-commoncpp@gnu.org; Thu, 15 May 2003 09:06:08 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19GIQw-0005vk-00
	for bug-commoncpp@gnu.org; Thu, 15 May 2003 09:06:07 -0400
Received: from postman.ateme.net ([217.167.236.59])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19GIQv-0005rH-00
	for bug-commoncpp@gnu.org; Thu, 15 May 2003 09:06:05 -0400
Received: from localhost (localhost.localdomain [127.0.0.1])
	by postman.ateme.net (Postfix) with ESMTP
	id 054672812A; Thu, 15 May 2003 15:05:57 +0200 (CEST)
Received: from pc183 (pc-183.ateme.net [172.16.16.183])
	by postman.ateme.net (Postfix) with SMTP
	id CD71E28129; Thu, 15 May 2003 15:05:56 +0200 (CEST)
Message-ID: <002401c31ae2$b9f1f9c0$b71010ac@pc183>
From: =?iso-8859-1?Q?=C9tienne_Dupuis?= <e.dupuis@ateme.fr>
To: "Federico Montesino Pouzols" <fedemp@altern.org>
References: <002b01c3147a$276e94f0$b71010ac@pc183>
	<20030515121256.GB25441@bulbasaur.rediris.es>
Date: Thu, 15 May 2003 15:05:58 +0200
Organization: ATEME
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Virus-Scanned: by F-Prot 3.12d
X-Mailman-Approved-At: Fri, 16 May 2003 09:02:17 -0400
cc: bug-commoncpp@gnu.org
Subject: Re: Thread.join() ?
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: =?iso-8859-1?Q?=C9tienne_Dupuis?= <e.dupuis@ateme.fr>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 15 May 2003 13:07:18 -0000

Greetings,

I found the answer in a recent post by yourself; a joinSem.post() was
missing in Thread::close(). Adding it solved the problem.

Thanks, Étienne



----- Original Message ----- 
From: "Federico Montesino Pouzols" <fedemp@altern.org>
To: "Étienne Dupuis" <e.dupuis@ateme.fr>
Cc: <bug-commoncpp@gnu.org>; "Ismaël Djima" <i.djima@ateme.fr>
Sent: Thursday, May 15, 2003 2:12 PM
Subject: Re: Thread.join() ?



I have just tested you example with the code in CVS and it
works fine. It may be an issue with your glibc or your kernel, as join
is a recent addition and I had not ever seen it failing. Also, the
strange behaviour of yield suggest that there is something very weird
in you system.




From MAILER-DAEMON Sat May 17 05:03:26 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19GxZU-00029I-00
	for mharc-bug-commoncpp@gnu.org; Sat, 17 May 2003 05:01:40 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19GxYs-00009g-00
	for bug-commoncpp@gnu.org; Sat, 17 May 2003 05:01:02 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19GxYa-00080c-00
	for bug-commoncpp@gnu.org; Sat, 17 May 2003 05:00:46 -0400
Received: from pool-138-89-45-96.mad.east.verizon.net ([138.89.45.96]
	helo=home.bayonne.dyndns.org)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 19GxYX-0007ob-00
	for bug-commoncpp@gnu.org; Sat, 17 May 2003 05:00:41 -0400
Received: from 192.168.1.104 ([192.168.1.104])
	by home.bayonne.dyndns.org (8.11.6/8.11.6) with ESMTP id h4H9pOF16972;
	Sat, 17 May 2003 05:51:24 -0400
From: David Sugar <dyfet@ostel.com>
To: Axel Waggershauser <awagger@web.de>, bug-commoncpp@gnu.org
Date: Sat, 17 May 2003 04:52:37 -0400
User-Agent: KMail/1.5
References: <1053085793.895.34.camel@strand>
In-Reply-To: <1053085793.895.34.camel@strand>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200305170452.37160.dyfet@ostel.com>
Subject: Re: put typedefs in config.h into namespace ost?
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 17 May 2003 09:01:39 -0000

I believe where we normally choose to come up with these are from their 
absense in the target systems header.  If we are using these convenience 
types internally alone, then they could be moved to private.h, but I think 
external libraries and even some apps now expect these to exist/be defined 
for them in the Common C++ headers...I would have to review that aspect, but 
you may be correct that we could move then into the ost namespace.

On Friday 16 May 2003 07:49 am, Axel Waggershauser wrote:
> Hi,
>
> I have a problem using libcommonc++ together with libtiff, since both
> typedef the same types (int16, int32, etc.). My workaround is to put
> these typedefs in config.h into the namespace ost.
>
> Would it be possible to adopt this fix to the library, so I don't have
> to patch it everytime, or does anybody know of a better solution?
>
> Thanks, Axel.
>
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp




From MAILER-DAEMON Sat May 17 15:08:57 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19H70c-0001Lp-00
	for mharc-bug-commoncpp@gnu.org; Sat, 17 May 2003 15:06:18 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19H70V-000151-00
	for bug-commoncpp@gnu.org; Sat, 17 May 2003 15:06:11 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19H70S-0000yQ-00
	for bug-commoncpp@gnu.org; Sat, 17 May 2003 15:06:08 -0400
Received: from subversions.gnu.org ([199.232.41.2])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19H70J-0000eG-00
	for bug-commoncpp@gnu.org; Sat, 17 May 2003 15:05:59 -0400
Received: from www-data by subversions.gnu.org with local (Exim 4.20)
	id 19H70T-0001UD-E0; Sat, 17 May 2003 15:06:09 -0400
To: bug-commoncpp@gnu.org,awagger@web.de,fedemp@altern.org
From: nobody@savannah.gnu.org
X-Savannah-Project: commoncpp
X-Savannah-Artifact: bug
X-Savannah-Artifact-ID: 3315
Message-Id: <E19H70T-0001UD-E0@subversions.gnu.org>
Sender: www-data <www-data@subversions.gnu.org>
Date: Sat, 17 May 2003 15:06:09 -0400
Subject: [Bug #3315] problems with ftp code in Borland C++ Builder
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 17 May 2003 19:06:17 -0000



=================== BUG #3315: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3315&group_id=89

Changes by: Federico Montesino Pouzols <fedemp@altern.org>
Date: Sat 05/17/2003 at 21:06 (Europe/Madrid)

            What     | Removed                   | Added
---------------------------------------------------------------------------
          Resolution | Later                     | Fixed
              Status | Open                      | Closed


------------------ Additional Follow-up Comments ----------------------------
Yes, it seems the best solution for now. It is in CVS.



=================== BUG #3315: FULL BUG SNAPSHOT ===================


Submitted by: awagger                 Project: commonc++                    
Submitted on: Thu 04/24/2003 at 00:36
Category:  None                       Severity:  5 - Major                  
Bug Group:  None                      Resolution:  Fixed                    
Assigned to:  fedemp                  Status:  Closed                       

Summary:  problems with ftp code in Borland C++ Builder

Original Submission:  I found (and fixed) two problems with the ftp code in libcommonc++2-1.0.9 when using the Borland C++ Builder (version 5).

1) I had to comment out line ftp.cpp:647 in method FTPSocket::DirEntry::parse(string li):

    str.get();  // skip space

since the mentioned space seemed to be included in the variable "junk", filled in the line bevore (ftp.cpp:646):

    str >> access >> junk >> user >> group >> size >> junk >> junk >> junk;


I don't know if it is an istream operator implementation problem or a unix <-> windows problem.


2) I had to change line ftp.cpp:482:

    ofstream f( lfilename.c_str() );

by explicitly specifying binary output mode like this:

    ofstream f( lfilename.c_str(),
        std::ios::out|std::ios::trunc|std::ios::binary );

otherwise the char '\n' got written as two bytes (as usual in windows in text-mode). So this is clearly a unix <-> windows porting problem. But I think, it should be perfectly ok, to use the same code for unix, since the result should be the same.



Follow-up Comments
*******************

-------------------------------------------------------
Date: Sat 05/17/2003 at 21:06       By: fedemp
Yes, it seems the best solution for now. It is in CVS.

-------------------------------------------------------
Date: Fri 05/16/2003 at 13:05       By: awagger
I still don't know where exactly the problem number 1) comes from, but a fix that does not break the lib on any other platform but still fixes the issue with the BCB is of course:

#ifndef __BORLANDC__
    str.get(); // skip space
#endif /* __BORLANDC__ */

-------------------------------------------------------
Date: Sun 05/11/2003 at 15:02       By: fedemp

 The second issue is fixed in CVS. As for the first one, I
suspect that your proposed change will break the library on
other platforms. Does anyone know if this happens because of
the istream implementation of Borland c++?.



CC List
*******

CC Address                          | Comment
------------------------------------+-----------------------------
bug-commoncpp@gnu.org               | 



No files currently attached


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=3315&group_id=89



From MAILER-DAEMON Mon May 19 09:06:20 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 19Hjti-0003yx-00
	for mharc-bug-commoncpp@gnu.org; Mon, 19 May 2003 08:37:46 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 19HaT8-0000G3-00
	for bug-commoncpp@gnu.org; Sun, 18 May 2003 22:33:42 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 19HaT6-0000Fa-00
	for bug-commoncpp@gnu.org; Sun, 18 May 2003 22:33:41 -0400
Received: from mx-s0.dreamwiz.com ([211.39.128.135])
	by monty-python.gnu.org with esmtp (Exim 4.10.13)
	id 19HaT6-0000Ev-00
	for bug-commoncpp@gnu.org; Sun, 18 May 2003 22:33:40 -0400
Received: from mail12.dreamwiz.com (mail12.dreamwiz.com [211.39.128.32])
	by mx-s0.dreamwiz.com (8.12.9/8.12.9) with ESMTP id h4J2Xal5020732
	for <bug-commoncpp@gnu.org>; Mon, 19 May 2003 11:33:36 +0900 (KST)
Received: from localhost (localhost [127.0.0.1])
	by mail12.dreamwiz.com (8.12.9/8.12.9) with ESMTP id h4J2XZ96082988
	for <bug-commoncpp@gnu.org>; Mon, 19 May 2003 11:33:35 +0900 (KST)
Message-Id: <200305190233.h4J2XZ96082988@mail12.dreamwiz.com>
Date: Mon, 19 May 2003 11:33:34 +0900 (KST)
From: =?EUC-KR?B?ua7HysHW?= <pjmun@dreamwiz.com>
To: bug-commoncpp@gnu.org
Organization: 
X-Sender-IP: 203.224.137.59
X-Sender-ID: pjmun@dreamwiz.com
X-Priority: 3
X-Mailer: DreamWiz Web-Mailer V1.70
X-DreamWiz-Data: receive_check=1;save=mail12.dreamwiz.com:pjmun:Sent:341;
MIME-Version: 1.0
Content-Type: MULTIPART/ALTERNATIVE; BOUNDARY="0-442436695-1053311615=:82979"
X-Mailman-Approved-At: Mon, 19 May 2003 08:37:45 -0400
Subject: [question]error in configure
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 19 May 2003 02:33:43 -0000

--0-442436695-1053311615=:82979
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII

hello 
let me introcuce myself..
my name is pilju mun , from korea.
i have a question about configure .

can i get advice to compile commoncpp?
have a nice day~
=============================================================
SMS:/usr/local>uname -a
HP-UX SMS B.11.11 U 9000/800 175484605 unlimited-user license
SMS:/usr/local/commoncpp2-1.0.9>./configure
loading cache ./config.cache
checking host system type... hppa2.0w-hp-hpux11.11
checking target system type... hppa2.0w-hp-hpux11.11
checking build system type... hppa2.0w-hp-hpux11.11
checking for gcc... gcc
checking whether the C compiler (gcc  ) works... yes
checking whether the C compiler (gcc  ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking how to run the C preprocessor... gcc -E
checking for strerror in -lcposix... no
checking for minix/config.h... no
checking for MSC environment... no
checking for Cygwin environment... no
checking for mingw32 environment... no
checking for ld used by GCC... /usr/ccs/bin/ld
checking if the linker (/usr/ccs/bin/ld) is GNU ld... no
checking for /usr/ccs/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -p
checking whether ln -s works... yes
checking how to recognise dependant libraries... file_magic (s[0-9][0-9][0-9]|PA-RISC[0-9].[0-9]) shared library
checking for object suffix... o
checking for executable suffix... configure: error: installation or configuration problem: compiler cannot create executables.
=============================================================


-------------------------------------------------
Your Life on the Net
DreamWiz Free Mail @ http://www.dreamwiz.com/


--0-442436695-1053311615=:82979
Content-Type: TEXT/HTML; CHARSET=EUC-KR
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mx-s0.dreamwiz.com id
	h4J2Xal5020732

<HTML>
<BODY>

<BR>hello=20
<BR>let me introcuce myself..
<BR>my name is pilju mun , from korea.
<BR>i have a question about configure .
<BR>
<BR>can i get advice to compile commoncpp?
<BR>have a nice day~
<BR>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
<BR>SMS:/usr/local>uname -a
<BR>HP-UX SMS B.11.11 U 9000/800 175484605 unlimited-user license
<BR>SMS:/usr/local/commoncpp2-1.0.9>./configure
<BR>loading cache ./config.cache
<BR>checking host system type... hppa2.0w-hp-hpux11.11
<BR>checking target system type... hppa2.0w-hp-hpux11.11
<BR>checking build system type... hppa2.0w-hp-hpux11.11
<BR>checking for gcc... gcc
<BR>checking whether the C compiler (gcc  ) works... yes
<BR>checking whether the C compiler (gcc  ) is a cross-compiler... no
<BR>checking whether we are using GNU C... yes
<BR>checking whether gcc accepts -g... yes
<BR>checking how to run the C preprocessor... gcc -E
<BR>checking for strerror in -lcposix... no
<BR>checking for minix/config.h... no
<BR>checking for MSC environment... no
<BR>checking for Cygwin environment... no
<BR>checking for mingw32 environment... no
<BR>checking for ld used by GCC... /usr/ccs/bin/ld
<BR>checking if the linker (/usr/ccs/bin/ld) is GNU ld... no
<BR>checking for /usr/ccs/bin/ld option to reload object files... -r
<BR>checking for BSD-compatible nm... /usr/bin/nm -p
<BR>checking whether ln -s works... yes
<BR>checking how to recognise dependant libraries... file_magic (s[0-9][0=
-9][0-9]|PA-RISC[0-9].[0-9]) shared library
<BR>checking for object suffix... o
<BR>checking for executable suffix... configure: error: installation or c=
onfiguration problem: compiler cannot create executables.
<BR>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
<BR>
<BR>
<BR></BODY>
</HTML>

<BR>
<a HREF=3D"http://www.dreamwiz.com/" TARGET=3D_blank><img SRC=3D"http://m=
ail.dreamwiz.com/pjmun/cgi-bin/receive_check.cgi?mailbox=3DSent&uid_valid=
ity=3D00000000000968250159&uid=3D00000000000000000341,X00000&key=3D45bf74=
3303144c21a6151cc9ff137f09" WIDTH=3D108 HEIGHT=3D21 BORDER=3D"0"></a><spa=
n style=3D"font-size: 9pt; font-family:=B1=BC=B8=B2; color: #494949; text=
-decoration: none;">=BB=FD=C8=B0=C0=CE=C5=CD=B3=DD =B5=E5=B8=B2=C0=A7=C1=EE=
 http://www.dreamwiz.com</span><br><img src=3D"http://i.dreamwiz.com/dw/k=
o/mw/mail/def/n.gif" width=3D1 height=3D5 border=3D"0"><br>
<img src=3D"http://i.dreamwiz.com/dw/ko/n.gif" width=3D4 height=3D1 borde=
r=3D"0"><img src=3D"http://i.dreamwiz.com/dw/ko/co/secimg4.gif" width=3D3=
0 height=3D35 align=3D"absmiddle" border=3D"0">
<a href=3D"http://avatar.dreamwiz.com"><span style=3D"font-size: 9pt; fon=
t-family:=B1=BC=B8=B2; color: #494949; text-decoration: none;">[=BE=C6=B9=
=D9=C5=B8] =BE=C6=B9=D9=C5=B8 =B2=D9=B9=CC=BC=CC=B3=AA=BF=E4? =C0=CC=C1=A6=
 =B8=DA=C1=F6=B0=D4 <font color=3D"red">=BE=C6=B9=D9=C5=B8</font> =B2=D9=B9=
=CC=B0=ED, =B4=EB=C8=AD=B9=E6=BF=A1=BC=AD =B8=B8=B3=AA=BF=E4.</a><br>
<img src=3D"http://i.dreamwiz.com/dw/ko/n.gif" width=3D5 height=3D1 borde=
r=3D"0"><img src=3D"http://i.dreamwiz.com/dw/ko/tel1.gif" align=3D"absmid=
dle" border=3D"0" >
<a href=3D"http://life.dreamwiz.com/sv/tel/tel_3.htm"><span style=3D"font=
-size: 9pt; font-family:=B1=BC=B8=B2; color: #494949; text-decoration: no=
ne;">[=BB=FD=C8=B0=C1=A4=BA=B8] <font color=3D"red">=B1=B9=C1=A6=C0=FC=C8=
=AD =BF=E4=B1=DD=BA=F1=B1=B3</font>, =C0=DF=B8=B8 =B0=F1=B6=F3=BE=B2=B8=E9=
 =BA=D0=B4=E7 1000=BF=F8=C0=CC =C0=FD=BE=E0=B5=CB=B4=CF=B4=D9.</font></a>=
<br>



--0-442436695-1053311615=:82979--



From MAILER-DAEMON Sat May 24 12:09:25 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19JbYm-00027O-JA
	for mharc-bug-commoncpp@gnu.org; Sat, 24 May 2003 12:07:52 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19JbKw-0007k3-FF
	for bug-commoncpp@gnu.org; Sat, 24 May 2003 11:53:34 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19JbKC-0006aY-N7
	for bug-commoncpp@gnu.org; Sat, 24 May 2003 11:52:52 -0400
Received: from smtp-out.comcast.net ([24.153.64.113])
	by monty-python.gnu.org with esmtp (Exim 4.20)
	id 19JbK4-0006Cf-TG
	for bug-commoncpp@gnu.org; Sat, 24 May 2003 11:52:40 -0400
Received: from mlsrock (pcp03787787pcs.mplsnt01.sc.comcast.net [68.58.236.16])
 by mtaout03.icomcast.net
 (iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003))
 with ESMTP id <0HFE001G5ER4XL@mtaout03.icomcast.net> for
 bug-commoncpp@gnu.org; Sat, 24 May 2003 11:52:16 -0400 (EDT)
Date: Sat, 24 May 2003 11:54:08 -0400 (EDT)
From: Chris Ahlstrom <ahlstromc@comcast.net>
X-X-Sender: ahlstrom@mlsrock
To: bug-commoncpp@gnu.org
Message-id: <Pine.LNX.4.55.0305241151420.7721@mlsrock>
MIME-version: 1.0
Content-type: multipart/mixed; boundary="Boundary_(ID_9ohk0KCliMst7UfmEqPyKw)"
X-Mailman-Approved-At: Sat, 24 May 2003 12:07:51 -0400
Subject: Portage issues
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: Chris Ahlstrom <ahlstromc@comcast.net>
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Sat, 24 May 2003 15:53:35 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.
  Send mail to mime@docserver.cac.washington.edu for more info.

--Boundary_(ID_9ohk0KCliMst7UfmEqPyKw)
Content-type: TEXT/PLAIN; charset=US-ASCII
Content-transfer-encoding: 7BIT

The attachment is a small text file showing issues uncovered trying
to eliminate warnings under gcc 3.2, Borland bcc32 5.5, Visual C++ 6,
and Visual C++ .NET.

Hope you can use this information.  CC++2 is cool!

Chris Ahlstrom
ahlstromc@comcast.net


--Boundary_(ID_9ohk0KCliMst7UfmEqPyKw)
Content-id: <Pine.LNX.4.55.0305241154080.7721@mlsrock>
Content-type: TEXT/plain; name=cc2-vids-changes.txt
Content-transfer-encoding: 7BIT
Content-disposition: attachment; filename=cc2-vids-changes.txt
Content-description: 

cc2-vids-changes.txt Chris Ahlstrom 05/24/2003

This document lists the changes that need to be merged into the
Common C++ code base when new versions of Common C++ are downloaded
and installed.

src
=================

   date.cpp
   ==============

      void Time::setTime(char *str, size_t size)
      {
         //
         // ca 11/26/2002
         // char *min;
         //

      FIXED: This fix is apparently already made in 1.0.10, so we don't have to
             do it for VIDS.

      
      // ca 11/04/2002

      Datetime::Datetime(tm *dt) :
        Date(dt), Time(dt)
      {}

      FIXED

      
      // ca 11/04/2002

      Datetime::Datetime(int year, unsigned month, unsigned day,
               int hour, int minute, int second) :
        Date(year, month, day), Time(hour, minute, second)
      {}

      FIXED

      // ca 11/04/2002

      Datetime::Datetime() : Date(), Time()
      {}

      Not FIXED, and new functionality added.  We must fix by adding the two
      initializers shown above.

      
      // ca 11/04/2002

      #ifdef WIN32
         last = /*std*/ ::strftime(buffer, 64, format, tbp);
      #else
         last = std::strftime(buffer, 64, format, tbp);
      #endif

      Not FIXED.  We should try a better way to make this fix.
      And also DOCUMENT OUR FIX properly.


   digest.cpp
   ==============

      //
      // ca 11/26/2002
      // Clean up time.
      //

      #ifdef _MSC_VER
      #pragma warning ( disable : 4355 )  // 'this' used in base init list
      #endif

      This code is added just before the first #include.
      Look into putting it into "private.h" instead.


   fifo.cpp
   ==============

      //
      // ca 05/12/2003
      // This header file is incompatible with Borland C++ Builder 4.  Luckily,
      // it is not necessary for Borland C++, either!
      //

      #ifndef __BORLANDC__
      #include <sys/stat.h>
      #endif

      This code is wrapped around the sys/stat.h declaration.


   keydata.cpp
   ==============
   
      //
      // ca 11/26/2002
      // Clean up time.
      //

      #ifdef _MSC_VER
      #pragma warning ( disable : 4018 )  // signed/unsigned mismatch
      #endif

      unsigned Keydata::getIndex(char **data, int max)
      {

      This code is placed before the above routine.


   numbers.cpp
   ==============
   
      //
      // ca 11/26/2002
      // Clean up time.
      //

      #ifdef _MSC_VER
      #pragma warning ( disable : 4244 )  // conversion from long to char
      #endif

      void Number::setValue(long value)
      {

      This code is placed before the above routine.


   serial.cpp
   ==============

      //
      // ca 11/26/2002
      // Clean up time.
      //

      #ifdef _MSC_VER
      #pragma warning ( disable : 4355 )  // 'this' used in base init list
      #endif

      This code is added just before the first #include.
      Look into putting it into "private.h" instead.


   slog.cpp
   ==============

      //
      // ca 11/26/2002
      // Clean up time.
      //

      #ifdef _MSC_VER
      #pragma warning ( disable : 4355 )  // 'this' used in base init list
      #endif

      This code is added just before the first #include.
      Look into putting it into "private.h" instead.


   socket.cpp
   ==============

      //
      // ca 11/26/2002
      // Clean up time.
      //

      #ifdef _MSC_VER
      #pragma warning ( disable : 4355 )  // 'this' used in base init list
      #endif

      This code is added just before the first #include.
      Look into putting it into "private.h" instead.

      
      //**************************************************************************
      // ca 11/26/2002
      // std::string doesn't handle the usage of null pointers in its
      // constructor.  Therefore, we get bogus exceptions having nothing
      // to do with any real problem.   So we now guarantee that there
      // is an informative string.
      //--------------------------------------------------------------------------

      #ifdef	COMMON_STD_EXCEPTION

	      case Thread::throwException:
		      {
               static const char * const msg =
                  "Socket::error() thrown with null string";      // ca 11/26/2002

			      SockException ex = string(errs == 0 ? msg : errs);
			      throw ex;
		      }

      #endif
         
      FIXED.  The authors now set a null string.  Our fix is better, but we
              should just accept their fix.


   thread.cpp
   ==============

      //
      // ca 05/12/2003
      // Only the Borland compiler catches that there is no identifier for
      // the typedef.  So we insert one just to satisfy that compiler.
      //

      typedef enum { 
	      THREAD_TYPE_NORMAL=0, 
	      THREAD_TYPE_MAIN, 
	      THREAD_TYPE_POSIX,
	      THREAD_TYPE_DUMMY
      } __BC_THREAD_TYPE;                 // ca 05/12/2003

      FIXED. However, it is fixed in the following way, and we should edit our
             code if need be:

      typedef enum ThreadType { 
	      threadTypeNormal=0, 
	      threadTypeMain, 
	      threadTypePosix,
	      threadTypeDummy
      } ThreadType;

include
=================

   socket.h
   ==============

      //
      // ca 05/15/2003
      // Visual C++ /W4 cleanup; commented unused parameters

	   void setPeer(const InetHostAddress & /*ia*/ , tpport_t /*port*/ ) {};

      Added the commenting shown.


      //
      // ca 05/15/2003
      // Visual C++ /W4 cleanup; commented unused parameters

	   virtual bool onAccept(const InetHostAddress & /*ia*/, tpport_t /*port*/ )
		   {return true;};

      Added the commenting shown.

      //
      // ca 05/15/2003
      // Visual C++ /W4 cleanup; commented unused parameters

	   inline InetHostAddress getSender(tpport_t * /*port*/ ) const
		   {return InetHostAddress();};

      Added the commenting shown.

      //
      // ca 05/15/2003
      // Visual C++ /W4 cleanup; commented unused parameters

	   virtual void onUpdate(unsigned char /*buf*/ )
		   {return;};

      Added the commenting shown.

      //
      // ca 05/15/2003
      // Visual C++ /W4 cleanup; commented unused parameters

	   virtual void onCallback(SocketPort * /*port*/ )
		   {return;};

      Added the commenting shown.


--Boundary_(ID_9ohk0KCliMst7UfmEqPyKw)--



From MAILER-DAEMON Thu May 29 08:52:08 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19LMsi-0003Vw-Bu
	for mharc-bug-commoncpp@gnu.org; Thu, 29 May 2003 08:51:44 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19LLL9-0008SN-T2
	for bug-commoncpp@gnu.org; Thu, 29 May 2003 07:12:59 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19LLKe-0008Cw-8Q
	for bug-commoncpp@gnu.org; Thu, 29 May 2003 07:12:28 -0400
Received: from mail-r.hw.ac.uk ([137.195.101.211] helo=mail-r1.hw.ac.uk)
	by monty-python.gnu.org with esmtp (Exim 4.20)
	id 19LL3L-0005Aj-NL
	for bug-commoncpp@gnu.org; Thu, 29 May 2003 06:54:35 -0400
Received: from alive.ece.eps.hw.ac.uk ([137.195.182.28] helo=alive)
	by mail-r1.hw.ac.uk with esmtp (Exim 3.36 #1)
	id 19LL3E-0001rt-00
	for bug-commoncpp@gnu.org; Thu, 29 May 2003 11:54:28 +0100
From: "Jonathan Evans" <j.evans@hw.ac.uk>
To: <bug-commoncpp@gnu.org>
Date: Thu, 29 May 2003 11:57:38 +0100
Message-ID: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAew4WLvXfAEGtH6iFw9QK5MKAAAAQAAAAY8zvqVqegEWWTnV1wSqRCQEAAAAA@hw.ac.uk>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-MailScanner-Information: Please contact the ISP for more information
X-HW-MailScanner: Found to be clean
X-Mailman-Approved-At: Thu, 29 May 2003 08:51:42 -0400
Subject: BUG REPORT: cc++, 2V1.0.11
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/bug-commoncpp>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 29 May 2003 11:13:00 -0000

BUG REPORT:

File:     thread.cpp
Line:     617
Comment:  The "free" operation on the thread's "char _msgbuf[128]"
          member variable causes a segmentation fault when the
          standard destructor ("Thread::~Thread") is called.
Solution: Do not try and release the non-dynamically allocated
          variable with "free"

diff output
-----------

[root@pastis2 src]# diff thread.cpp thread.cpp.v11b 
617,619c617,619
< 	if(priv)
< 		if( priv->_msgbuf != NULL)
< 			free(priv->_msgbuf);
---
> //	if(priv)
> //		if( priv->_msgbuf != NULL)
> //			free(priv->_msgbuf);

PS The bug reporting address on:
      http://www.gnu.org/directory/commoncpp.html

is shown (incorrectly) as "bug-commonc++@gnu.org"

===============================================================
Dr Jonathan Evans
Ocean Systems Laboratory
Heriot-Watt University               E-Mail:   j.evans@hw.ac.uk
Edinburgh EH14 4AS                   Tel:  (+44)(0)131 451 3506
SCOTLAND, UK                         Fax:  (+44)(0)131 451 4155
===============================================================




