From MAILER-DAEMON Sat Jan 27 10:19:11 2007
Received: from mailman by lists.gnu.org with archive (Exim 4.43)
	id 1HApKh-000350-Hd
	for mharc-bug-commoncpp@gnu.org; Sat, 27 Jan 2007 10:19:11 -0500
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1HApKf-00034r-Bn
	for bug-commoncpp@gnu.org; Sat, 27 Jan 2007 10:19:09 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1HApKc-00034f-R9
	for bug-commoncpp@gnu.org; Sat, 27 Jan 2007 10:19:08 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1HApKc-00034c-L0
	for bug-commoncpp@gnu.org; Sat, 27 Jan 2007 10:19:06 -0500
Received: from mta066b.interbusiness.it ([85.37.17.66])
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1HApKc-0003Jc-97
	for bug-commoncpp@gnu.org; Sat, 27 Jan 2007 10:19:06 -0500
Received: from host123-160-static.29-87-b.business.telecomitalia.it (HELO
	[192.168.0.1]) ([87.29.160.123])
	by MTA066B.interbusiness.it with ESMTP; 27 Jan 2007 16:18:23 +0100
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAADP8ukVXHaB7/2dsb2JhbAAN
Message-ID: <45BB6D42.30306@bigfoot.com>
Date: Sat, 27 Jan 2007 16:18:26 +0100
From: Wakan <wakan@bigfoot.com>
User-Agent: Mozilla Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: bug-commoncpp@gnu.org
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
X-detected-kernel: FreeBSD 2.0-4.2
Subject: can't release mutex
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/bug-commoncpp>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Jan 2007 15:19:09 -0000

Hi,
I'm using commoncpp library in a project that includes a multithread 
server that
can accept many tcp connection and each connection generates a thread.
In this server I'm using a thirdy party proprietary library (compiled), 
that (as the producer says)
can't work in multithread environment.
As each connection thread needs to call functions of this thirdy party 
library, I've used a mutex to protect the piece of
code where this external library function is called.
In this way I can use this library fine, because all calls are 
serialized and the protected function is called by one thread each time.
This is an example:
...
    while(1) {
        if(isPending(pendingInput)) {
                mutex.enterMutex();
                ---> protected function call (a function that can't work 
in multithread env) <---       
                mutex.leaveMutex();
       }
    }
...
in 99% of cases it works fine. But it accidentally happens that a thread 
can't exit from the mutex
maybe because the thirdy party function freezes itself.
When this happens, the server can accept other connections, soit still 
works, but each thread can't enter in the mutex proteced piece of code.
I'm thinking about something, like a timeout, that exits the mutex after 
a time, if the thread is not exiting...
Can someone help me to resolve this problem? Are there other solutions?
Thanks in advance,
Regards
Carlo



From MAILER-DAEMON Sat Jan 27 13:43:10 2007
Received: from mailman by lists.gnu.org with archive (Exim 4.43)
	id 1HAsW6-0007qn-Jl
	for mharc-bug-commoncpp@gnu.org; Sat, 27 Jan 2007 13:43:10 -0500
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1HAsW5-0007pg-Up
	for bug-commoncpp@gnu.org; Sat, 27 Jan 2007 13:43:09 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1HAsW5-0007on-9t
	for bug-commoncpp@gnu.org; Sat, 27 Jan 2007 13:43:09 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1HAsW5-0007oc-4c
	for bug-commoncpp@gnu.org; Sat, 27 Jan 2007 13:43:09 -0500
Received: from sccrmhc13.comcast.net ([204.127.200.83])
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1HAsW4-0008BI-Px
	for bug-commoncpp@gnu.org; Sat, 27 Jan 2007 13:43:08 -0500
Received: from phoenix (c-67-169-21-105.hsd1.ca.comcast.net[67.169.21.105])
	by comcast.net (sccrmhc13) with SMTP
	id <2007012718430601300hsrsee>; Sat, 27 Jan 2007 18:43:07 +0000
From: "Conrad T. Pino" <Conrad@Pino.com>
To: "Wakan" <wakan@bigfoot.com>,
	<bug-commoncpp@gnu.org>
Date: Sat, 27 Jan 2007 10:43:07 -0800
Message-ID: <NBBBKGBBDBMONCPMINHBMEBDLGAB.Conrad@Pino.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="ISO-8859-15"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1896
Importance: Normal
In-Reply-To: <45BB6D42.30306@bigfoot.com>
X-detected-kernel: NetCache Data OnTap 5.x
Cc: 
Subject: RE: can't release mutex
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/bug-commoncpp>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Jan 2007 18:43:10 -0000

You're on the right track.  Please pardon my rusty recollection syntax.
Revise:

	mutex.enterMutex();

to a form that accepts a timeout.  This example won't compile:

	const int timeout = 500;

	while (1) {
		if ( isPending( pendingInput ) ) {
			int result = mutex.enterMutex( timeout );

			if ( result == success ) {
				---> protected function call (a function that can't work 
				in multithread env) <---       
				mutex.leaveMutex();
			} else {
				// do something else with pending input
			}
		}
	}

While the above will implement your timeout idea it does nothing about
the fundamental problem.  When the library "breaks" can be discoverd
and the blocked mutex/thread combination can be cancelled/restared
HOWEVER PROPRIETARY LIBRARY STATE IS INCONSISTENT & LIKELY DANGEROUS.

If the library is dynamically loaded under your control then unload it
and reload it to get it back into a consistent state.  If it's auto or
static linked then you may have an unsolveable problem.

If a reliable system is your goal then one of these MUST be true:

		proprietary library NEVER fails
	OR
		proprietary library can be forced back to a consistent
		state because it has a reload or reinitialize method

Good luck.

> -----Original Message-----
> From: bug-commoncpp-bounces+conrad=pino.com@gnu.org
> [mailto:bug-commoncpp-bounces+conrad=pino.com@gnu.org]On Behalf Of Wakan
> Sent: Saturday, January 27, 2007 07:18
> To: bug-commoncpp@gnu.org
> Subject: can't release mutex
> 
> Hi,
> I'm using commoncpp library in a project that includes a multithread 
> server that
> can accept many tcp connection and each connection generates a thread.
> In this server I'm using a thirdy party proprietary library (compiled), 
> that (as the producer says)
> can't work in multithread environment.
> As each connection thread needs to call functions of this thirdy party 
> library, I've used a mutex to protect the piece of
> code where this external library function is called.
> In this way I can use this library fine, because all calls are 
> serialized and the protected function is called by one thread each time.
> This is an example:
> ...
>     while(1) {
>         if(isPending(pendingInput)) {
>                 mutex.enterMutex();
>                 ---> protected function call (a function that can't work 
> in multithread env) <---       
>                 mutex.leaveMutex();
>        }
>     }
> ...
> in 99% of cases it works fine. But it accidentally happens that a thread 
> can't exit from the mutex
> maybe because the thirdy party function freezes itself.
> When this happens, the server can accept other connections, soit still 
> works, but each thread can't enter in the mutex proteced piece of code.
> I'm thinking about something, like a timeout, that exits the mutex after 
> a time, if the thread is not exiting...
> Can someone help me to resolve this problem? Are there other solutions?
> Thanks in advance,
> Regards
> Carlo




From MAILER-DAEMON Sat Jan 27 15:04:58 2007
Received: from mailman by lists.gnu.org with archive (Exim 4.43)
	id 1HAtnG-0000v9-DH
	for mharc-bug-commoncpp@gnu.org; Sat, 27 Jan 2007 15:04:58 -0500
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1HAtnF-0000v3-4v
	for bug-commoncpp@gnu.org; Sat, 27 Jan 2007 15:04:57 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1HAtnD-0000uj-Ho
	for bug-commoncpp@gnu.org; Sat, 27 Jan 2007 15:04:55 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1HAtnD-0000ug-D5
	for bug-commoncpp@gnu.org; Sat, 27 Jan 2007 15:04:55 -0500
Received: from mta072d.interbusiness.it ([85.37.17.72])
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1HAtnC-0002NV-Lj
	for bug-commoncpp@gnu.org; Sat, 27 Jan 2007 15:04:55 -0500
Received: from host123-160-static.29-87-b.business.telecomitalia.it (HELO
	[192.168.0.1]) ([87.29.160.123])
	by MTA072D.interbusiness.it with ESMTP; 27 Jan 2007 21:04:52 +0100
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAAHY/u0VXHaB7/2dsb2JhbAANgwA3iV0
Message-ID: <45BBB067.8080604@bigfoot.com>
Date: Sat, 27 Jan 2007 21:04:55 +0100
From: Wakan <wakan@bigfoot.com>
User-Agent: Mozilla Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: "Conrad T. Pino" <Conrad@Pino.com>
References: <NBBBKGBBDBMONCPMINHBMEBDLGAB.Conrad@Pino.com>
In-Reply-To: <NBBBKGBBDBMONCPMINHBMEBDLGAB.Conrad@Pino.com>
Content-Type: text/html; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit
X-detected-kernel: FreeBSD 2.0-4.2
Cc: bug-commoncpp@gnu.org
Subject: Re: can't release mutex
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/bug-commoncpp>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Jan 2007 20:04:57 -0000

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-15"
 http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Thanks very much for your kind reply!<br>
I think the problem is elsewhere...<br>
When the thread the calls the proprietary function never runs to the<br>
mutex.leaveMutex(), say because the function doesn't be able to exit
for an internal break, <br>
all other threads will continue to loop in vain....because the mutex
will never be released.<br>
What I need is something (maybe another thread) that checks if a thread
is jammed (with a timer)<br>
and in this case tell it to exit, or kill it (because if a thread is
jammed, can't go on...so can't check for timeouts or exit flags)...<br>
Sorry for my poor english....hope it is clear enought<br>
Thanks in advance for you help,<br>
Carlo<br>
<br>
<br>
Conrad T. Pino ha scritto:
<blockquote cite="midNBBBKGBBDBMONCPMINHBMEBDLGAB.Conrad@Pino.com"
 type="cite">
  <pre wrap="">You're on the right track.  Please pardon my rusty recollection syntax.
Revise:

	mutex.enterMutex();

to a form that accepts a timeout.  This example won't compile:

	const int timeout = 500;

	while (1) {
		if ( isPending( pendingInput ) ) {
			int result = mutex.enterMutex( timeout );

			if ( result == success ) {
				---&gt; protected function call (a function that can't work 
				in multithread env) &lt;---       
				mutex.leaveMutex();
			} else {
				// do something else with pending input
			}
		}
	}

While the above will implement your timeout idea it does nothing about
the fundamental problem.  When the library "breaks" can be discoverd
and the blocked mutex/thread combination can be cancelled/restared
HOWEVER PROPRIETARY LIBRARY STATE IS INCONSISTENT &amp; LIKELY DANGEROUS.

If the library is dynamically loaded under your control then unload it
and reload it to get it back into a consistent state.  If it's auto or
static linked then you may have an unsolveable problem.

If a reliable system is your goal then one of these MUST be true:

		proprietary library NEVER fails
	OR
		proprietary library can be forced back to a consistent
		state because it has a reload or reinitialize method

Good luck.

  </pre>
  <blockquote type="cite">
    <pre wrap="">-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:bug-commoncpp-bounces+conrad=pino.com@gnu.org">bug-commoncpp-bounces+conrad=pino.com@gnu.org</a>
[<a class="moz-txt-link-freetext" href="mailto:bug-commoncpp-bounces+conrad=pino.com@gnu.org">mailto:bug-commoncpp-bounces+conrad=pino.com@gnu.org</a>]On Behalf Of Wakan
Sent: Saturday, January 27, 2007 07:18
To: <a class="moz-txt-link-abbreviated" href="mailto:bug-commoncpp@gnu.org">bug-commoncpp@gnu.org</a>
Subject: can't release mutex

Hi,
I'm using commoncpp library in a project that includes a multithread 
server that
can accept many tcp connection and each connection generates a thread.
In this server I'm using a thirdy party proprietary library (compiled), 
that (as the producer says)
can't work in multithread environment.
As each connection thread needs to call functions of this thirdy party 
library, I've used a mutex to protect the piece of
code where this external library function is called.
In this way I can use this library fine, because all calls are 
serialized and the protected function is called by one thread each time.
This is an example:
...
    while(1) {
        if(isPending(pendingInput)) {
                mutex.enterMutex();
                ---&gt; protected function call (a function that can't work 
in multithread env) &lt;---       
                mutex.leaveMutex();
       }
    }
...
in 99% of cases it works fine. But it accidentally happens that a thread 
can't exit from the mutex
maybe because the thirdy party function freezes itself.
When this happens, the server can accept other connections, soit still 
works, but each thread can't enter in the mutex proteced piece of code.
I'm thinking about something, like a timeout, that exits the mutex after 
a time, if the thread is not exiting...
Can someone help me to resolve this problem? Are there other solutions?
Thanks in advance,
Regards
Carlo
    </pre>
  </blockquote>
  <pre wrap=""><!---->

__________ NOD32 2011 (20070127) Information __________

This message was checked by NOD32 antivirus system.
<a class="moz-txt-link-freetext" href="http://www.eset.com">http://www.eset.com</a>



  </pre>
</blockquote>
<br>
</body>
</html>



From MAILER-DAEMON Sat Jan 27 16:16:52 2007
Received: from mailman by lists.gnu.org with archive (Exim 4.43)
	id 1HAuuq-0004JN-34
	for mharc-bug-commoncpp@gnu.org; Sat, 27 Jan 2007 16:16:52 -0500
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Gqpph-0007FA-3B
	for bug-commoncpp@gnu.org; Sun, 03 Dec 2006 06:48:33 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Gqppe-0007Dq-LB
	for bug-commoncpp@gnu.org; Sun, 03 Dec 2006 06:48:31 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Gqppe-0007DZ-Eg
	for bug-commoncpp@gnu.org; Sun, 03 Dec 2006 06:48:30 -0500
Received: from [80.47.247.129] (helo=dell.purcell.id.au)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32)
	(Exim 4.52) id 1Gqppe-0000mi-46
	for bug-commoncpp@gnu.org; Sun, 03 Dec 2006 06:48:30 -0500
Received: from mark by dell.purcell.id.au with local (Exim 4.63)
	(envelope-from <msp@debian.org>)
	id 1Gqppa-0002jU-40; Sun, 03 Dec 2006 11:48:26 +0000
Content-Disposition: inline
From: Mark Purcell <msp@debian.org>
Organization: Debian GNU/Linux
To: bug-commoncpp@gnu.org,
 David Sugar <dyfet@ostel.com>
User-Agent: KMail/1.9.5
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200612031148.25738.msp@debian.org>
X-Mailman-Approved-At: Sat, 27 Jan 2007 16:16:50 -0500
Cc: Scott Edwards <debian@foss.daxal.com>, 399482-forwarded@bugs.debian.org
Subject: Fwd: Bug#399482: libcommoncpp2: build process cannot find ldconfig
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/bug-commoncpp>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
Date: Sun, 03 Dec 2006 11:48:33 -0000
X-Original-Date: Sun, 3 Dec 2006 11:48:23 +0000
X-List-Received-Date: Sun, 03 Dec 2006 11:48:33 -0000

David,

I have received a report about your install-local-data rule in libcommoncpp2.

Apparently you have made some assumptions about the target directory, which 
isn't always correct.

The full bug report is available at http://bugs.debian.org/399482.

Could I also ask you to maintain the Cc: in any replies to this issue, to keep 
the Debian Bug Tracking system informed.

Mark


----------  Forwarded Message  ----------

Subject: Bug#399482: libcommoncpp2: build process cannot find ldconfig
Date: Monday 20 November 2006 09:55
From: Steve Langasek <vorlon@debian.org>
To: Scott Edwards <debian@foss.daxal.com>, 399482@bugs.debian.org

severity 399482 important
thanks

On Sun, Nov 19, 2006 at 05:17:20PM +0000, Scott Edwards wrote:
> make[3]: Nothing to be done for `install-exec-am'.
> ---------------------------------------------------------------------------
>--- Hmm, looks like you forgot to add
> /usr/local/src/etch/libcommoncpp2-1.4.3/debian/tmp/usr/lib to
> /etc/ld.so.conf. I'll try to fix it for you (but pay attention to libtool's
> output
> next time, ok?)
> /bin/sh: line 1: /etc/ld.so.conf: Permission denied
>
> Well, that didn't work.  Remember to add
> /usr/local/src/etch/libcommoncpp2-1.4.3/debian/tmp/usr/lib to
> /etc/ld.so.conf if you want to use this library.
> ---------------------------------------------------------------------------
>--- /bin/sh: line 1: ldconfig: command not found
> make[3]: *** [install-data-local] Error 127

This is caused by a goofy install-data-local rule in the upstream Makefile
which checks whether the target directory is under /usr, and if so, munges
/etc/ld.so.conf along the way.  In general, the target directory when
building a Debian package will *not* be under /usr, so I'm downgrading this
report since it's specific to your build env.

Thanks,
--
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
vorlon@debian.org                                   http://www.debian.org/


_______________________________________________
Pkg-voip-maintainers mailing list
Pkg-voip-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-voip-maintainers

-------------------------------------------------------



From MAILER-DAEMON Sat Jan 27 16:16:52 2007
Received: from mailman by lists.gnu.org with archive (Exim 4.43)
	id 1HAuuq-0004Jh-FV
	for mharc-bug-commoncpp@gnu.org; Sat, 27 Jan 2007 16:16:52 -0500
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Gqq2g-0007c4-5p
	for bug-commoncpp@gnu.org; Sun, 03 Dec 2006 07:01:58 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Gqq2f-0007bI-FQ
	for bug-commoncpp@gnu.org; Sun, 03 Dec 2006 07:01:57 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Gqq2f-0007b2-11
	for bug-commoncpp@gnu.org; Sun, 03 Dec 2006 07:01:57 -0500
Received: from [80.47.247.129] (helo=dell.purcell.id.au)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32)
	(Exim 4.52) id 1Gqq2e-00030S-Dp
	for bug-commoncpp@gnu.org; Sun, 03 Dec 2006 07:01:56 -0500
Received: from mark by dell.purcell.id.au with local (Exim 4.63)
	(envelope-from <msp@debian.org>) id 1Gqq2c-0003Sr-8E
	for bug-commoncpp@gnu.org; Sun, 03 Dec 2006 12:01:54 +0000
Content-Disposition: inline
From: Mark Purcell <msp@debian.org>
Organization: Debian GNU/Linux
To: bug-commoncpp@gnu.org
User-Agent: KMail/1.9.5
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <200612031201.54236.msp@debian.org>
X-Mailman-Approved-At: Sat, 27 Jan 2007 16:16:50 -0500
Subject: Fwd: Bug#352123: libcommoncpp2-dev: slog should not cut after 128
	bytes
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/bug-commoncpp>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
Date: Sun, 03 Dec 2006 12:01:58 -0000
X-Original-Date: Sun, 3 Dec 2006 12:01:53 +0000
X-List-Received-Date: Sun, 03 Dec 2006 12:01:58 -0000



----------  Forwarded Message  ----------

Subject: Fwd: Bug#352123: libcommoncpp2-dev: slog should not cut after 128 
bytes
Date: Friday 10 February 2006 11:07
From: Mark Purcell <msp@debian.org>
To: bug-commoncpp@gnu.org
Cc: 352123-forwarded@bugs.debian.org, Stephan A Suerken <absurd@schlund.de>

David,

Please find a suggestion from a Debian GNU/Linux user on your logging in
libcommoncpp2.

Mark

----------  Forwarded Message  ----------

Subject: Bug#352123: libcommoncpp2-dev: slog should not cut after 128 bytes
Date: Friday 10 February 2006 08:12
From: Stephan A Suerken <absurd@schlund.de>
To: Debian Bug Tracking System <submit@bugs.debian.org>

Package: libcommoncpp2-dev
Version: 1.3.22-1
Severity: wishlist
Tags: patch

Hi,

the thread safe logging currently cut lines after 128 bytes; this is a
bit short for real life logs.

Ideally, lines should be unlimited ;). However, I suggest to increase
that to 256 as a quick fix:

$ absurd? diff private.h.orig private.h
55c55
<       char _msgbuf[128];
---

>       char _msgbuf[256];

Thanks,

Stephan

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.8-2-k7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages libcommoncpp2-dev depends on:
ii  libcommoncpp2-1.3c2a          1.3.22-1   A GNU package for creating
 portabl

libcommoncpp2-dev recommends no packages.

-- no debconf information
--
Stephan A Suerken <suerken|absurd@schlund.de>
Phone: +49.721.91347-393

Schlund + Partner AG, Karlsruhe

-------------------------------------------------------

-------------------------------------------------------



From MAILER-DAEMON Sat Jan 27 16:16:53 2007
Received: from mailman by lists.gnu.org with archive (Exim 4.43)
	id 1HAuur-0004KY-Ch
	for mharc-bug-commoncpp@gnu.org; Sat, 27 Jan 2007 16:16:53 -0500
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1H1reE-0008IC-Rn
	for bug-commoncpp@gnu.org; Tue, 02 Jan 2007 16:58:18 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1H1reB-0008E1-Ti
	for bug-commoncpp@gnu.org; Tue, 02 Jan 2007 16:58:18 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1H1reB-0008Dp-Qy
	for bug-commoncpp@gnu.org; Tue, 02 Jan 2007 16:58:15 -0500
Received: from [196.40.59.21] (helo=interamerica.net)
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1H1reB-00044b-D7
	for bug-commoncpp@gnu.org; Tue, 02 Jan 2007 16:58:15 -0500
Received: from [196.40.59.109] (account mrodriguez@siscocr.com)
	by interamerica.net (CommuniGate Pro WEBUSER 5.1.4)
	with HTTP id 184607434 for bug-commoncpp@gnu.org;
	Tue, 02 Jan 2007 15:58:07 -0600
From: "Mario Rodriguez Villanea" <mrodriguez@siscocr.com>
To: bug-commoncpp@gnu.org
X-Mailer: CommuniGate Pro WebUser v5.1.4
Message-ID: <web-184607434@interamerica.net>
MIME-Version: 1.0
Content-Type: text/plain;charset="iso-8859-1";format="flowed"
Content-Transfer-Encoding: 8bit
X-Mailman-Approved-At: Sat, 27 Jan 2007 16:16:50 -0500
Subject: error compiling Common C++ under solaris
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/bug-commoncpp>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
Date: Tue, 02 Jan 2007 21:58:19 -0000
X-Original-Date: Tue, 02 Jan 2007 15:58:07 -0600
X-List-Received-Date: Tue, 02 Jan 2007 21:58:19 -0000

I'm using Common C++ in solaris, but when I include math.h 
I got the error below.  If I compile my application under 
linux the application works fine.  The problem is that 
math.h defines an struct named exception which conflicts 
with the #include <exception> declared in exception.h. 
 Any suggestion ?



g++ -c Lock.cpp  -L/usr/local/lib -Iincludes -I. 
 -I/usr/include -Wall -O2 -MD
-D_GNU_SOURCE -D_THREAD_SAFE -g3 -pg -DSOLARIS 
 -D__EXTENSIONS__ -D_REENTRANT
In file included from includes/cc++/exception.h:25,
                  from includes/cc++/address.h:20,
                  from includes/cc++/socket.h:15,
                  from includes/NodesMetadata.h:29,
                  from includes/Msg.h:40,
                  from includes/DsmController.h:33,
                  from Lock.cpp:18:
/usr/local/lib/gcc-lib/sparc-sun-solaris2.8/2.95.2/include/exception:13: 
redefinition of `struct exception'
/usr/include/math.h:92: previous definition here
In file included from includes/Msg.h:40,
                  from includes/DsmController.h:33,
                  from Lock.cpp:18:
make[1]: *** [Lock.o] Error 1



From MAILER-DAEMON Sat Jan 27 16:16:53 2007
Received: from mailman by lists.gnu.org with archive (Exim 4.43)
	id 1HAuur-0004Kg-I4
	for mharc-bug-commoncpp@gnu.org; Sat, 27 Jan 2007 16:16:53 -0500
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1H1reZ-00008c-VF
	for bug-commoncpp@gnu.org; Tue, 02 Jan 2007 16:58:40 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1H1reZ-00007m-9x
	for bug-commoncpp@gnu.org; Tue, 02 Jan 2007 16:58:39 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1H1reZ-00007e-47
	for bug-commoncpp@gnu.org; Tue, 02 Jan 2007 16:58:39 -0500
Received: from [64.233.184.231] (helo=wr-out-0506.google.com)
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1H1reY-0004Aa-MT
	for bug-commoncpp@gnu.org; Tue, 02 Jan 2007 16:58:38 -0500
Received: by wr-out-0506.google.com with SMTP id i30so907299wra
	for <bug-commoncpp@gnu.org>; Tue, 02 Jan 2007 13:58:38 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:mime-version:content-type;
	b=qvPXwrFFTzGUtJOQ8+lRLXDWpQnz8v9D7aVHC8vXEnlqQ2VuYP9DMBpYhku83fLuhNjWkmxoKtOEnNlIDEIingg4G5wwW4cff2deY/ixObqwLscdGViIjOHxc5GcR7ixgy73Li1DlJ7EQW35oAHjHoeU8sjS5HxXU+cSn/QG8VY=
Received: by 10.90.101.19 with SMTP id y19mr5584481agb.1167775118340;
	Tue, 02 Jan 2007 13:58:38 -0800 (PST)
Received: by 10.90.51.3 with HTTP; Tue, 2 Jan 2007 13:58:38 -0800 (PST)
Message-ID: <93a4a3040701021358i6ff4d31y9ba26aba461b699b@mail.gmail.com>
From: "Mario Rodriguez" <rvillane@gmail.com>
To: bug-commoncpp@gnu.org
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_58781_11371021.1167775118318"
X-Mailman-Approved-At: Sat, 27 Jan 2007 16:16:50 -0500
Subject: error compiling Common C++ under Solaris
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/bug-commoncpp>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
Date: Tue, 02 Jan 2007 21:58:40 -0000
X-Original-Date: Tue, 2 Jan 2007 15:58:38 -0600
X-List-Received-Date: Tue, 02 Jan 2007 21:58:40 -0000

------=_Part_58781_11371021.1167775118318
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I'm using Common C++ in solaris, but when I include math.h I got the error
below.  If I compile my application under linux the application works fine.
The problem is that math.h defines an struct named exception which conflicts
with the #include <exception> declared in exception.h.  Any suggestion ?



g++ -c Lock.cpp  -L/usr/local/lib -Iincludes -I.  -I/usr/include -Wall -O2
-MD
-D_GNU_SOURCE -D_THREAD_SAFE -g3 -pg -DSOLARIS  -D__EXTENSIONS__
-D_REENTRANT
In file included from includes/cc++/exception.h:25,
                 from includes/cc++/address.h:20,
                 from includes/cc++/socket.h:15,
                 from includes/NodesMetadata.h:29,
                 from includes/Msg.h:40,
                 from includes/DsmController.h:33,
                 from Lock.cpp:18:
/usr/local/lib/gcc-lib/sparc-sun-solaris2.8/2.95.2/include/exception:13:
redefinition of `struct exception'
/usr/include/math.h:92: previous definition here
In file included from includes/Msg.h:40,
                 from includes/DsmController.h:33,
                 from Lock.cpp:18:
make[1]: *** [Lock.o] Error 1


-- 
Mario Rodriguez

------=_Part_58781_11371021.1167775118318
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I&#39;m using Common C++ in solaris, but when I include math.h I got the error below.&nbsp; If I compile my application under linux the application works fine.&nbsp; The problem is that math.h defines an struct named exception which conflicts with the #include &lt;exception&gt; declared in 
exception.h.&nbsp; Any suggestion ?<br><br><br><br>g++ -c Lock.cpp&nbsp; -L/usr/local/lib -Iincludes -I.&nbsp; -I/usr/include -Wall -O2 -MD<br>-D_GNU_SOURCE -D_THREAD_SAFE -g3 -pg -DSOLARIS&nbsp; -D__EXTENSIONS__ -D_REENTRANT<br>In file included from includes/cc++/exception.h:25,
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; from includes/cc++/address.h:20,<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; from includes/cc++/socket.h:15,<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; from includes/NodesMetadata.h:29,<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; from includes/Msg.h:40,<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; from includes/DsmController.h:33,
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; from Lock.cpp:18:<br>/usr/local/lib/gcc-lib/sparc-sun-solaris2.8/2.95.2/include/exception:13: redefinition of `struct exception&#39;<br>/usr/include/math.h:92: previous definition here<br>In file included from includes/Msg.h:40,
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; from includes/DsmController.h:33,<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; from Lock.cpp:18:<br>make[1]: *** [Lock.o] Error 1<br><br clear="all"><br>-- <br>Mario Rodriguez

------=_Part_58781_11371021.1167775118318--



From MAILER-DAEMON Sat Jan 27 16:16:53 2007
Received: from mailman by lists.gnu.org with archive (Exim 4.43)
	id 1HAuur-0004KP-4o
	for mharc-bug-commoncpp@gnu.org; Sat, 27 Jan 2007 16:16:53 -0500
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Gv3iq-0001id-Ka
	for bug-commoncpp@gnu.org; Thu, 14 Dec 2006 22:26:56 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Gv3ip-0001fr-6s
	for bug-commoncpp@gnu.org; Thu, 14 Dec 2006 22:26:56 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Gv3ip-0001fc-0x
	for bug-commoncpp@gnu.org; Thu, 14 Dec 2006 22:26:55 -0500
Received: from [201.242.9.69] (helo=zeus.mizrahi.com.ve)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1Gv3io-0000m6-QQ
	for bug-commoncpp@gnu.org; Thu, 14 Dec 2006 22:26:55 -0500
Received: from alan by zeus.mizrahi.com.ve with local (Exim 4.62)
	(envelope-from <alan@mizrahi.com.ve>) id 1Gv3kU-00074g-EF
	for bug-commoncpp@gnu.org; Thu, 14 Dec 2006 23:28:38 -0400
From: Alan Mizrahi <alan+bugs@mizrahi.com.ve>
To: bug-commoncpp@gnu.org
User-Agent: KMail/1.9.5
X-PGP-Key: http://www.mizrahi.com.ve/alan/pubkey.txt
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200612142328.37872.alan+bugs@mizrahi.com.ve>
Sender: Alan Mizrahi <alan@mizrahi.com.ve>
X-Mailman-Approved-At: Sat, 27 Jan 2007 16:16:50 -0500
Subject: commoncpp 1.5.0 doesn't build with fstack-protector
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/bug-commoncpp>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
Date: Fri, 15 Dec 2006 03:26:57 -0000
X-Original-Date: Thu, 14 Dec 2006 23:28:36 -0400
X-List-Received-Date: Fri, 15 Dec 2006 03:26:57 -0000

Hello,

Unfortunately commoncpp2-1.5.0 doesn't build when using -fstack-protector gcc 
flags.
The stack protector flags are supported in gcc 4.1.1, could you verify this?

Regards,

-- 
Alan Mizrahi



From MAILER-DAEMON Sat Jan 27 16:16:52 2007
Received: from mailman by lists.gnu.org with archive (Exim 4.43)
	id 1HAuuq-0004Jy-Qz
	for mharc-bug-commoncpp@gnu.org; Sat, 27 Jan 2007 16:16:52 -0500
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1GsNXy-0007QA-EJ
	for bug-commoncpp@gnu.org; Thu, 07 Dec 2006 13:00:38 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1GsNXu-0007Py-HY
	for bug-commoncpp@gnu.org; Thu, 07 Dec 2006 13:00:37 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1GsNXu-0007Pv-DT
	for bug-commoncpp@gnu.org; Thu, 07 Dec 2006 13:00:34 -0500
Received: from [80.47.237.207] (helo=dell.purcell.id.au)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32)
	(Exim 4.52) id 1GsNXt-0004Dx-Qs
	for bug-commoncpp@gnu.org; Thu, 07 Dec 2006 13:00:34 -0500
Received: from mark by dell.purcell.id.au with local (Exim 4.63)
	(envelope-from <msp@debian.org>)
	id 1GsNXl-0002WH-PU; Thu, 07 Dec 2006 18:00:26 +0000
From: Mark Purcell <msp@debian.org>
Organization: Debian GNU/Linux
To: bug-commoncpp@gnu.org,
 David Sugar <dyfet@ostel.com>
User-Agent: KMail/1.9.5
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200612071800.25772.msp@debian.org>
X-Mailman-Approved-At: Sat, 27 Jan 2007 16:16:50 -0500
Cc: Jan Niehusmann <jan@gondor.com>, 402009-forwarded@bugs.debian.org
Subject: libcommoncpp2-1.5-0 version 1.5.3-1 is ABI incompatible with
	version 1.5.1-4
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/bug-commoncpp>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
Date: Thu, 07 Dec 2006 18:00:38 -0000
X-Original-Date: Thu, 7 Dec 2006 18:00:23 +0000
X-List-Received-Date: Thu, 07 Dec 2006 18:00:38 -0000

David,

It would appear that commoncpp2-1.5.3 isn't ABI compatible with previous 
releases due to changes with ost::Thread::isRunning 

http://bugs.debian.org/402009

Mark

----------  Forwarded Message  ----------

Subject: Bug#402009: #402009
Date: Thursday 07 December 2006 14:35
From: Mikael Magnusson <mikaelmagnusson@glocalnet.net>
To: control@bugs.debian.org
Cc: 402009@bugs.debian.org

package twinkle
reassign 402009 libcommoncpp2-1.5-0 1.5.3-1
severity 402009 grave
thanks


since ost::Thread::isRunning has been changed to const.

$ nm -D libccgnu2-1.5.so.0.0.3 |grep isRunning
00019486 T _ZNK3ost6Thread9isRunningEv

$ nm -D libccgnu2-1.5.so.0.0.1 |grep isRunning
00019476 T _ZN3ost6Thread9isRunningEv


_______________________________________________
Pkg-voip-maintainers mailing list
Pkg-voip-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-voip-maintainers

-------------------------------------------------------



From MAILER-DAEMON Sat Jan 27 16:22:43 2007
Received: from mailman by lists.gnu.org with archive (Exim 4.43)
	id 1HAv0V-0006nQ-F6
	for mharc-bug-commoncpp@gnu.org; Sat, 27 Jan 2007 16:22:43 -0500
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1HAv0T-0006mQ-Ov
	for bug-commoncpp@gnu.org; Sat, 27 Jan 2007 16:22:41 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1HAv0Q-0006lw-Ci
	for bug-commoncpp@gnu.org; Sat, 27 Jan 2007 16:22:40 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1HAv0Q-0006lt-78
	for bug-commoncpp@gnu.org; Sat, 27 Jan 2007 16:22:38 -0500
Received: from outbound.mailhop.org ([63.208.196.171])
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1HAv0P-0003Dq-UL
	for bug-commoncpp@gnu.org; Sat, 27 Jan 2007 16:22:38 -0500
Received: from pool-72-76-21-88.nwrknj.fios.verizon.net ([72.76.21.88]
	helo=[192.168.1.90])
	by outbound.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256)
	(Exim 4.63) (envelope-from <dyfet@gnutelephony.org>)
	id 1HAv0N-0001YQ-Tn; Sat, 27 Jan 2007 16:22:36 -0500
X-Mail-Handler: MailHop Outbound by DynDNS
X-Originating-IP: 72.76.21.88
X-Report-Abuse-To: abuse@dyndns.com (see
	http://www.mailhop.org/outbound/abuse.html for abuse reporting
	information)
X-MHO-User: dyfet
Message-ID: <45BBC29A.8060608@gnutelephony.org>
Date: Sat, 27 Jan 2007 16:22:34 -0500
From: David Sugar <dyfet@gnutelephony.org>
User-Agent: Thunderbird 1.5.0.9 (X11/20061219)
MIME-Version: 1.0
To: "Conrad T. Pino" <Conrad@Pino.com>
References: <NBBBKGBBDBMONCPMINHBMEBDLGAB.Conrad@Pino.com>
In-Reply-To: <NBBBKGBBDBMONCPMINHBMEBDLGAB.Conrad@Pino.com>
X-Enigmail-Version: 0.94.0.0
Content-Type: multipart/mixed; boundary="------------010508090708070302010601"
X-detected-kernel: FreeBSD 4.6-4.9
Cc: bug-commoncpp@gnu.org
Subject: Re: can't release mutex
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/bug-commoncpp>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Jan 2007 21:22:42 -0000

This is a multi-part message in MIME format.
--------------010508090708070302010601
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit

I think what he really wants to do is use the Common C++ Semaphore with
a count of 1, since semaphore can block with a "timeout", and with a "1"
count in effect acts as a mutex...

The larger question though of what to do with the stuck thread, perhaps
from a broken library, is important also.  He could cancel the thread in
question if it timed out, and put cleanup code in the thread destructor
when he invokes delete to join it, but if the library allocated
resources he cannot determine for them to get cleanly deallocated.

Conrad T. Pino wrote:
> You're on the right track.  Please pardon my rusty recollection syntax.
> Revise:
> 
> 	mutex.enterMutex();
> 
> to a form that accepts a timeout.  This example won't compile:
> 
> 	const int timeout = 500;
> 
> 	while (1) {
> 		if ( isPending( pendingInput ) ) {
> 			int result = mutex.enterMutex( timeout );
> 
> 			if ( result == success ) {
> 				---> protected function call (a function that can't work 
> 				in multithread env) <---       
> 				mutex.leaveMutex();
> 			} else {
> 				// do something else with pending input
> 			}
> 		}
> 	}
> 
> While the above will implement your timeout idea it does nothing about
> the fundamental problem.  When the library "breaks" can be discoverd
> and the blocked mutex/thread combination can be cancelled/restared
> HOWEVER PROPRIETARY LIBRARY STATE IS INCONSISTENT & LIKELY DANGEROUS.
> 
> If the library is dynamically loaded under your control then unload it
> and reload it to get it back into a consistent state.  If it's auto or
> static linked then you may have an unsolveable problem.
> 
> If a reliable system is your goal then one of these MUST be true:
> 
> 		proprietary library NEVER fails
> 	OR
> 		proprietary library can be forced back to a consistent
> 		state because it has a reload or reinitialize method
> 
> Good luck.
> 
>> -----Original Message-----
>> From: bug-commoncpp-bounces+conrad=pino.com@gnu.org
>> [mailto:bug-commoncpp-bounces+conrad=pino.com@gnu.org]On Behalf Of Wakan
>> Sent: Saturday, January 27, 2007 07:18
>> To: bug-commoncpp@gnu.org
>> Subject: can't release mutex
>>
>> Hi,
>> I'm using commoncpp library in a project that includes a multithread 
>> server that
>> can accept many tcp connection and each connection generates a thread.
>> In this server I'm using a thirdy party proprietary library (compiled), 
>> that (as the producer says)
>> can't work in multithread environment.
>> As each connection thread needs to call functions of this thirdy party 
>> library, I've used a mutex to protect the piece of
>> code where this external library function is called.
>> In this way I can use this library fine, because all calls are 
>> serialized and the protected function is called by one thread each time.
>> This is an example:
>> ...
>>     while(1) {
>>         if(isPending(pendingInput)) {
>>                 mutex.enterMutex();
>>                 ---> protected function call (a function that can't work 
>> in multithread env) <---       
>>                 mutex.leaveMutex();
>>        }
>>     }
>> ...
>> in 99% of cases it works fine. But it accidentally happens that a thread 
>> can't exit from the mutex
>> maybe because the thirdy party function freezes itself.
>> When this happens, the server can accept other connections, soit still 
>> works, but each thread can't enter in the mutex proteced piece of code.
>> I'm thinking about something, like a timeout, that exits the mutex after 
>> a time, if the thread is not exiting...
>> Can someone help me to resolve this problem? Are there other solutions?
>> Thanks in advance,
>> Regards
>> Carlo
> 
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://lists.gnu.org/mailman/listinfo/bug-commoncpp

--------------010508090708070302010601
Content-Type: text/x-vcard; charset=utf-8;
 name="dyfet.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="dyfet.vcf"

begin:vcard
fn:David Sugar
n:Sugar;David
org:GNU Telephony
email;internet:dyfet@gnutelephony.org
tel;work:+1 201 215 2609
url:http://www.gnutelephony.org
version:2.1
end:vcard


--------------010508090708070302010601--



From MAILER-DAEMON Sat Jan 27 16:23:48 2007
Received: from mailman by lists.gnu.org with archive (Exim 4.43)
	id 1HAv1Y-00071c-3E
	for mharc-bug-commoncpp@gnu.org; Sat, 27 Jan 2007 16:23:48 -0500
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1HAv1W-000711-1s
	for bug-commoncpp@gnu.org; Sat, 27 Jan 2007 16:23:46 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1HAv1V-00070d-7R
	for bug-commoncpp@gnu.org; Sat, 27 Jan 2007 16:23:45 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1HAv1U-00070W-SL
	for bug-commoncpp@gnu.org; Sat, 27 Jan 2007 16:23:44 -0500
Received: from outbound.mailhop.org ([63.208.196.171])
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1HAv1U-0003dg-I4
	for bug-commoncpp@gnu.org; Sat, 27 Jan 2007 16:23:44 -0500
Received: from pool-72-76-21-88.nwrknj.fios.verizon.net ([72.76.21.88]
	helo=[192.168.1.90])
	by outbound.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256)
	(Exim 4.63) (envelope-from <dyfet@gnutelephony.org>)
	id 1HAv1T-0001ms-Px; Sat, 27 Jan 2007 16:23:43 -0500
X-Mail-Handler: MailHop Outbound by DynDNS
X-Originating-IP: 72.76.21.88
X-Report-Abuse-To: abuse@dyndns.com (see
	http://www.mailhop.org/outbound/abuse.html for abuse reporting
	information)
X-MHO-User: dyfet
Message-ID: <45BBC2DF.3060205@gnutelephony.org>
Date: Sat, 27 Jan 2007 16:23:43 -0500
From: David Sugar <dyfet@gnutelephony.org>
User-Agent: Thunderbird 1.5.0.9 (X11/20061219)
MIME-Version: 1.0
To: Mark Purcell <msp@debian.org>
References: <200612031201.54236.msp@debian.org>
In-Reply-To: <200612031201.54236.msp@debian.org>
X-Enigmail-Version: 0.94.0.0
Content-Type: multipart/mixed; boundary="------------000508050707070800000700"
X-detected-kernel: FreeBSD 4.6-4.9
Cc: bug-commoncpp@gnu.org
Subject: Re: Fwd: Bug#352123: libcommoncpp2-dev: slog should not cut after
 128	bytes
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/bug-commoncpp>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Jan 2007 21:23:46 -0000

This is a multi-part message in MIME format.
--------------000508050707070800000700
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

This will break abi, so I will do it for a new 1.6 release set...

Mark Purcell wrote:
> 
> ----------  Forwarded Message  ----------
> 
> Subject: Fwd: Bug#352123: libcommoncpp2-dev: slog should not cut after 128 
> bytes
> Date: Friday 10 February 2006 11:07
> From: Mark Purcell <msp@debian.org>
> To: bug-commoncpp@gnu.org
> Cc: 352123-forwarded@bugs.debian.org, Stephan A Suerken <absurd@schlund.de>
> 
> David,
> 
> Please find a suggestion from a Debian GNU/Linux user on your logging in
> libcommoncpp2.
> 
> Mark
> 
> ----------  Forwarded Message  ----------
> 
> Subject: Bug#352123: libcommoncpp2-dev: slog should not cut after 128 bytes
> Date: Friday 10 February 2006 08:12
> From: Stephan A Suerken <absurd@schlund.de>
> To: Debian Bug Tracking System <submit@bugs.debian.org>
> 
> Package: libcommoncpp2-dev
> Version: 1.3.22-1
> Severity: wishlist
> Tags: patch
> 
> Hi,
> 
> the thread safe logging currently cut lines after 128 bytes; this is a
> bit short for real life logs.
> 
> Ideally, lines should be unlimited ;). However, I suggest to increase
> that to 256 as a quick fix:
> 
> $ absurd? diff private.h.orig private.h
> 55c55
> <       char _msgbuf[128];
> ---
> 
>>       char _msgbuf[256];
> 
> Thanks,
> 
> Stephan
> 
> -- System Information:
> Debian Release: testing/unstable
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: i386 (i686)
> Shell:  /bin/sh linked to /bin/bash
> Kernel: Linux 2.6.8-2-k7
> Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
> 
> Versions of packages libcommoncpp2-dev depends on:
> ii  libcommoncpp2-1.3c2a          1.3.22-1   A GNU package for creating
>  portabl
> 
> libcommoncpp2-dev recommends no packages.
> 
> -- no debconf information
> --
> Stephan A Suerken <suerken|absurd@schlund.de>
> Phone: +49.721.91347-393
> 
> Schlund + Partner AG, Karlsruhe
> 
> -------------------------------------------------------
> 
> -------------------------------------------------------
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://lists.gnu.org/mailman/listinfo/bug-commoncpp

--------------000508050707070800000700
Content-Type: text/x-vcard; charset=utf-8;
 name="dyfet.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="dyfet.vcf"

begin:vcard
fn:David Sugar
n:Sugar;David
org:GNU Telephony
email;internet:dyfet@gnutelephony.org
tel;work:+1 201 215 2609
url:http://www.gnutelephony.org
version:2.1
end:vcard


--------------000508050707070800000700--



From MAILER-DAEMON Sat Jan 27 16:25:01 2007
Received: from mailman by lists.gnu.org with archive (Exim 4.43)
	id 1HAv2j-0007Iv-FO
	for mharc-bug-commoncpp@gnu.org; Sat, 27 Jan 2007 16:25:01 -0500
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1HAv2h-0007Id-Uv
	for bug-commoncpp@gnu.org; Sat, 27 Jan 2007 16:24:59 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1HAv2g-0007IR-Hd
	for bug-commoncpp@gnu.org; Sat, 27 Jan 2007 16:24:58 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1HAv2g-0007IO-DN
	for bug-commoncpp@gnu.org; Sat, 27 Jan 2007 16:24:58 -0500
Received: from outbound.mailhop.org ([63.208.196.171])
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1HAv2g-0003l0-3V
	for bug-commoncpp@gnu.org; Sat, 27 Jan 2007 16:24:58 -0500
Received: from pool-72-76-21-88.nwrknj.fios.verizon.net ([72.76.21.88]
	helo=[192.168.1.90])
	by outbound.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256)
	(Exim 4.63) (envelope-from <dyfet@gnutelephony.org>)
	id 1HAv2f-0001wF-A2; Sat, 27 Jan 2007 16:24:57 -0500
X-Mail-Handler: MailHop Outbound by DynDNS
X-Originating-IP: 72.76.21.88
X-Report-Abuse-To: abuse@dyndns.com (see
	http://www.mailhop.org/outbound/abuse.html for abuse reporting
	information)
X-MHO-User: dyfet
Message-ID: <45BBC328.506@gnutelephony.org>
Date: Sat, 27 Jan 2007 16:24:56 -0500
From: David Sugar <dyfet@gnutelephony.org>
User-Agent: Thunderbird 1.5.0.9 (X11/20061219)
MIME-Version: 1.0
To: Mark Purcell <msp@debian.org>
References: <200612031148.25738.msp@debian.org>
In-Reply-To: <200612031148.25738.msp@debian.org>
X-Enigmail-Version: 0.94.0.0
Content-Type: multipart/mixed; boundary="------------000901000909030402010507"
X-detected-kernel: FreeBSD 4.6-4.9
Cc: David Sugar <dyfet@ostel.com>, bug-commoncpp@gnu.org,
	Scott Edwards <debian@foss.daxal.com>, 399482-forwarded@bugs.debian.org
Subject: Re: Fwd: Bug#399482: libcommoncpp2: build process cannot find
	ldconfig
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/bug-commoncpp>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Jan 2007 21:25:00 -0000

This is a multi-part message in MIME format.
--------------000901000909030402010507
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

This was already removed in 1.5.3...

Mark Purcell wrote:
> David,
> 
> I have received a report about your install-local-data rule in libcommoncpp2.
> 
> Apparently you have made some assumptions about the target directory, which 
> isn't always correct.
> 
> The full bug report is available at http://bugs.debian.org/399482.
> 
> Could I also ask you to maintain the Cc: in any replies to this issue, to keep 
> the Debian Bug Tracking system informed.
> 
> Mark
> 
> 
> ----------  Forwarded Message  ----------
> 
> Subject: Bug#399482: libcommoncpp2: build process cannot find ldconfig
> Date: Monday 20 November 2006 09:55
> From: Steve Langasek <vorlon@debian.org>
> To: Scott Edwards <debian@foss.daxal.com>, 399482@bugs.debian.org
> 
> severity 399482 important
> thanks
> 
> On Sun, Nov 19, 2006 at 05:17:20PM +0000, Scott Edwards wrote:
>> make[3]: Nothing to be done for `install-exec-am'.
>> ---------------------------------------------------------------------------
>> --- Hmm, looks like you forgot to add
>> /usr/local/src/etch/libcommoncpp2-1.4.3/debian/tmp/usr/lib to
>> /etc/ld.so.conf. I'll try to fix it for you (but pay attention to libtool's
>> output
>> next time, ok?)
>> /bin/sh: line 1: /etc/ld.so.conf: Permission denied
>>
>> Well, that didn't work.  Remember to add
>> /usr/local/src/etch/libcommoncpp2-1.4.3/debian/tmp/usr/lib to
>> /etc/ld.so.conf if you want to use this library.
>> ---------------------------------------------------------------------------
>> --- /bin/sh: line 1: ldconfig: command not found
>> make[3]: *** [install-data-local] Error 127
> 
> This is caused by a goofy install-data-local rule in the upstream Makefile
> which checks whether the target directory is under /usr, and if so, munges
> /etc/ld.so.conf along the way.  In general, the target directory when
> building a Debian package will *not* be under /usr, so I'm downgrading this
> report since it's specific to your build env.
> 
> Thanks,
> --
> Steve Langasek                   Give me a lever long enough and a Free OS
> Debian Developer                   to set it on, and I can move the world.
> vorlon@debian.org                                   http://www.debian.org/
> 
> 
> _______________________________________________
> Pkg-voip-maintainers mailing list
> Pkg-voip-maintainers@lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/pkg-voip-maintainers
> 
> -------------------------------------------------------
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://lists.gnu.org/mailman/listinfo/bug-commoncpp

--------------000901000909030402010507
Content-Type: text/x-vcard; charset=utf-8;
 name="dyfet.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="dyfet.vcf"

begin:vcard
fn:David Sugar
n:Sugar;David
org:GNU Telephony
email;internet:dyfet@gnutelephony.org
tel;work:+1 201 215 2609
url:http://www.gnutelephony.org
version:2.1
end:vcard


--------------000901000909030402010507--



From MAILER-DAEMON Sat Jan 27 16:26:08 2007
Received: from mailman by lists.gnu.org with archive (Exim 4.43)
	id 1HAv3o-0007XK-PP
	for mharc-bug-commoncpp@gnu.org; Sat, 27 Jan 2007 16:26:08 -0500
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1HAv3n-0007XF-KJ
	for bug-commoncpp@gnu.org; Sat, 27 Jan 2007 16:26:07 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1HAv3m-0007X3-64
	for bug-commoncpp@gnu.org; Sat, 27 Jan 2007 16:26:06 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1HAv3m-0007X0-18
	for bug-commoncpp@gnu.org; Sat, 27 Jan 2007 16:26:06 -0500
Received: from outbound.mailhop.org ([63.208.196.171])
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1HAv3l-0003r8-Iv
	for bug-commoncpp@gnu.org; Sat, 27 Jan 2007 16:26:05 -0500
Received: from pool-72-76-21-88.nwrknj.fios.verizon.net ([72.76.21.88]
	helo=[192.168.1.90])
	by outbound.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256)
	(Exim 4.63) (envelope-from <dyfet@gnutelephony.org>)
	id 1HAv3k-00025z-Rh; Sat, 27 Jan 2007 16:26:04 -0500
X-Mail-Handler: MailHop Outbound by DynDNS
X-Originating-IP: 72.76.21.88
X-Report-Abuse-To: abuse@dyndns.com (see
	http://www.mailhop.org/outbound/abuse.html for abuse reporting
	information)
X-MHO-User: dyfet
Message-ID: <45BBC36C.3030303@gnutelephony.org>
Date: Sat, 27 Jan 2007 16:26:04 -0500
From: David Sugar <dyfet@gnutelephony.org>
User-Agent: Thunderbird 1.5.0.9 (X11/20061219)
MIME-Version: 1.0
To: Mark Purcell <msp@debian.org>
References: <200612071800.25772.msp@debian.org>
In-Reply-To: <200612071800.25772.msp@debian.org>
X-Enigmail-Version: 0.94.0.0
Content-Type: multipart/mixed; boundary="------------000100070007070207040306"
X-detected-kernel: FreeBSD 4.6-4.9
Cc: David Sugar <dyfet@ostel.com>, bug-commoncpp@gnu.org,
	Jan Niehusmann <jan@gondor.com>, 402009-forwarded@bugs.debian.org
Subject: Re: libcommoncpp2-1.5-0 version 1.5.3-1 is ABI incompatible with
 version 1.5.1-4
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/bug-commoncpp>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Jan 2007 21:26:07 -0000

This is a multi-part message in MIME format.
--------------000100070007070207040306
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

ick...we should have changed the abi rev level then...it got missed...

Mark Purcell wrote:
> David,
> 
> It would appear that commoncpp2-1.5.3 isn't ABI compatible with previous 
> releases due to changes with ost::Thread::isRunning 
> 
> http://bugs.debian.org/402009
> 
> Mark
> 
> ----------  Forwarded Message  ----------
> 
> Subject: Bug#402009: #402009
> Date: Thursday 07 December 2006 14:35
> From: Mikael Magnusson <mikaelmagnusson@glocalnet.net>
> To: control@bugs.debian.org
> Cc: 402009@bugs.debian.org
> 
> package twinkle
> reassign 402009 libcommoncpp2-1.5-0 1.5.3-1
> severity 402009 grave
> thanks
> 
> 
> since ost::Thread::isRunning has been changed to const.
> 
> $ nm -D libccgnu2-1.5.so.0.0.3 |grep isRunning
> 00019486 T _ZNK3ost6Thread9isRunningEv
> 
> $ nm -D libccgnu2-1.5.so.0.0.1 |grep isRunning
> 00019476 T _ZN3ost6Thread9isRunningEv
> 
> 
> _______________________________________________
> Pkg-voip-maintainers mailing list
> Pkg-voip-maintainers@lists.alioth.debian.org
> http://lists.alioth.debian.org/mailman/listinfo/pkg-voip-maintainers
> 
> -------------------------------------------------------
> 
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://lists.gnu.org/mailman/listinfo/bug-commoncpp

--------------000100070007070207040306
Content-Type: text/x-vcard; charset=utf-8;
 name="dyfet.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="dyfet.vcf"

begin:vcard
fn:David Sugar
n:Sugar;David
org:GNU Telephony
email;internet:dyfet@gnutelephony.org
tel;work:+1 201 215 2609
url:http://www.gnutelephony.org
version:2.1
end:vcard


--------------000100070007070207040306--



From MAILER-DAEMON Sat Jan 27 16:26:39 2007
Received: from mailman by lists.gnu.org with archive (Exim 4.43)
	id 1HAv4J-0007db-1U
	for mharc-bug-commoncpp@gnu.org; Sat, 27 Jan 2007 16:26:39 -0500
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1HAv4H-0007dW-Mz
	for bug-commoncpp@gnu.org; Sat, 27 Jan 2007 16:26:37 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1HAv4F-0007dK-7h
	for bug-commoncpp@gnu.org; Sat, 27 Jan 2007 16:26:36 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1HAv4F-0007dH-2B
	for bug-commoncpp@gnu.org; Sat, 27 Jan 2007 16:26:35 -0500
Received: from outbound.mailhop.org ([63.208.196.171])
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1HAv4E-0003uk-RP
	for bug-commoncpp@gnu.org; Sat, 27 Jan 2007 16:26:34 -0500
Received: from pool-72-76-21-88.nwrknj.fios.verizon.net ([72.76.21.88]
	helo=[192.168.1.90])
	by outbound.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256)
	(Exim 4.63) (envelope-from <dyfet@gnutelephony.org>)
	id 1HAv4E-0002DR-2w; Sat, 27 Jan 2007 16:26:34 -0500
X-Mail-Handler: MailHop Outbound by DynDNS
X-Originating-IP: 72.76.21.88
X-Report-Abuse-To: abuse@dyndns.com (see
	http://www.mailhop.org/outbound/abuse.html for abuse reporting
	information)
X-MHO-User: dyfet
Message-ID: <45BBC389.2060502@gnutelephony.org>
Date: Sat, 27 Jan 2007 16:26:33 -0500
From: David Sugar <dyfet@gnutelephony.org>
User-Agent: Thunderbird 1.5.0.9 (X11/20061219)
MIME-Version: 1.0
To: Alan Mizrahi <alan+bugs@mizrahi.com.ve>
References: <200612142328.37872.alan+bugs@mizrahi.com.ve>
In-Reply-To: <200612142328.37872.alan+bugs@mizrahi.com.ve>
X-Enigmail-Version: 0.94.0.0
Content-Type: multipart/mixed; boundary="------------060702060605000008070801"
X-detected-kernel: FreeBSD 4.6-4.9
Cc: bug-commoncpp@gnu.org
Subject: Re: commoncpp 1.5.0 doesn't build with fstack-protector
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/bug-commoncpp>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Jan 2007 21:26:37 -0000

This is a multi-part message in MIME format.
--------------060702060605000008070801
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

I will see if this is still true with 1.5.5...

Alan Mizrahi wrote:
> Hello,
> 
> Unfortunately commoncpp2-1.5.0 doesn't build when using -fstack-protector gcc 
> flags.
> The stack protector flags are supported in gcc 4.1.1, could you verify this?
> 
> Regards,
> 

--------------060702060605000008070801
Content-Type: text/x-vcard; charset=utf-8;
 name="dyfet.vcf"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="dyfet.vcf"

YmVnaW46dmNhcmQNCmZuOkRhdmlkIFN1Z2FyDQpuOlN1Z2FyO0RhdmlkDQpvcmc6R05VIFRl
bGVwaG9ueQ0KZW1haWw7aW50ZXJuZXQ6ZHlmZXRAZ251dGVsZXBob255Lm9yZw0KdGVsO3dv
cms6KzEgMjAxIDIxNSAyNjA5DQp1cmw6aHR0cDovL3d3dy5nbnV0ZWxlcGhvbnkub3JnDQp2
ZXJzaW9uOjIuMQ0KZW5kOnZjYXJkDQoNCg==
--------------060702060605000008070801--



From MAILER-DAEMON Sun Jan 28 10:16:19 2007
Received: from mailman by lists.gnu.org with archive (Exim 4.43)
	id 1HBBlT-0007Dm-7L
	for mharc-bug-commoncpp@gnu.org; Sun, 28 Jan 2007 10:16:19 -0500
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1HBBlP-0007C5-RI
	for bug-commoncpp@gnu.org; Sun, 28 Jan 2007 10:16:15 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1HBBlP-0007Bt-Hu
	for bug-commoncpp@gnu.org; Sun, 28 Jan 2007 10:16:15 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1HBBlP-0007Bq-7S
	for bug-commoncpp@gnu.org; Sun, 28 Jan 2007 10:16:15 -0500
Received: from outbound.mailhop.org ([63.208.196.171])
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1HBBlO-0001nT-Ue
	for bug-commoncpp@gnu.org; Sun, 28 Jan 2007 10:16:15 -0500
Received: from pool-72-76-21-88.nwrknj.fios.verizon.net ([72.76.21.88]
	helo=[192.168.1.90])
	by outbound.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256)
	(Exim 4.63) (envelope-from <dyfet@gnutelephony.org>)
	id 1HBBlN-0006Um-Sc; Sun, 28 Jan 2007 10:16:14 -0500
X-Mail-Handler: MailHop Outbound by DynDNS
X-Originating-IP: 72.76.21.88
X-Report-Abuse-To: abuse@dyndns.com (see
	http://www.mailhop.org/outbound/abuse.html for abuse reporting
	information)
X-MHO-User: dyfet
Message-ID: <45BCBE3C.3030600@gnutelephony.org>
Date: Sun, 28 Jan 2007 10:16:12 -0500
From: David Sugar <dyfet@gnutelephony.org>
User-Agent: Thunderbird 1.5.0.9 (X11/20061219)
MIME-Version: 1.0
To: bug-commoncpp@gnu.org
References: <200612142328.37872.alan+bugs@mizrahi.com.ve>
	<45BBC389.2060502@gnutelephony.org>
In-Reply-To: <45BBC389.2060502@gnutelephony.org>
X-Enigmail-Version: 0.94.0.0
Content-Type: multipart/mixed; boundary="------------000600000505010906070109"
X-detected-kernel: FreeBSD 4.6-4.9
Cc: Federico Montesino Pouzols <fedemp@altern.org>,
	Werner Dittmann <Werner.Dittmann@t-online.de>,
	Alan Mizrahi <alan+bugs@mizrahi.com.ve>,
	Michel de Boer <michelboer@xs4all.nl>
Subject: Ideas for Common C++ 2.0...
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/bug-commoncpp>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Jan 2007 15:16:16 -0000

This is a multi-part message in MIME format.
--------------000600000505010906070109
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

This seemed like a good time to discuss some current ideas for common
c++ 2.0...

First, I have wanted to make object management smarter, and borrow a
little from objective-c.  Hence, we will have a new commonly used
virtual base class, "Object", which will include a release() virtual.
This can be used to form self refcounted objects (ala objective-c),
among other nice things.

More important, it will be used with two helper classes, auto_delete and
auto_release.  Auto_release is meant to be used to contain Object
pointers often created by the "new" operation (or a refcounted copy) for
an object that most often is generated in the thread's constructor, but
in any case is to be "released" when a thread terminates or is canceled.
 This provides a simple scheme for automatic management of threaded heap
resources.  A second helper, auto_delete, is meant to be used for stack
frame pointers that are to be released when a member function returns.

auto_release and auto_delete will be wrapped in (and most often used by)
a couple of templates that will use them as base classes and only offer
light inline type conversion methods, including pointer (like
auto/smart_ptr) and release (thread released pointer).  Hence, you might
have something like:

	pointer<mytype> myptr = new mytype...

How this differs from boost shared_ptr or std::auto_ptr is that we will
use a concrete base class for the actual implementation code rather than
carry it in the template, and the object being referenced will have a
common base also, and hence the template is only used as a wrapper for
implementing inline type safety and cast conversions.  Unlike in boost,
the behavior (deletion method, ref counting, etc) is not a part of the
pointer object which might be commonly instanciated, but rather the base
class of the object being pointed to.   This means that the pointer<xxx>
instance only has a single pointer, and not additional details like
refcount objects, delete methods, etc. The release (auto_release object)
only has the pointer and a linked list for releasables on the thread
base.  A file descriptor (or w32 Handle) could also be described through
a "releasable" object that invokes ::close (or CloseHandle).

We also would not have the overhead traditionally involved in templates
with complex inline/embedded methods that also often lead to large code
blocks generated both for each specific type invocation and in each
object module since where implementation is instantiated is not defined
for a template.  These templates may even work in broken Microsoft
compilers, such as the latest one, which cannot seem to embed
traditional templates (such as stl) in dll's at all.  This kind of
methodology of using a common base and a concrete helper class wrapped
in a typecasing template might also be useful to apply to building a
full and stl-like library that can be used successfully without template
bloat and compiler issues.

Another change will be in mutex/semaphore/rwlock locking.  These will
also be managed by two stack auto-functions, exclusive and shared, and
the Mutex/Semaphore/RWLock classes will also be constructed from
"virtual abstracts" for ExclusiveLock, SharedLock, and ReleaseLock so
they can be used with the generic shared/exclusive objects.  Hence, to
have a method lock like the java sync keyword, with an embedded Mutex in
the base:

	void myclass::mymethod(void) {
		int somevar = 0;
		exlusive lock(this);
		...

This will put an instance of lock on the stack frame, will lock the
mutex in the constructor of lock, and release it when ~lock() is called,
which happens on a return...A special macro, EXCLUSIVE, and SHARED, may
be added for simplicity when refercing mutexes/rwlocks/semaphores that
are constructed in the base class...

Hence, a Semaphore is a "shared" lock, a mutex an "exclusive" one, and a
rwlock is both, depending on whether your using the read or write lock
method...

Other changes I am considering include dropping of CCXX_NAMESPACE
wrapper, and just assuming any useful compiler has namespace.  Perhaps
with 1.6 we will add the new gcc visibility flag support.  With 2.0, we
will likely switch to the "gnu" namespace.   Also, I have looked at the
redhat "pthread library for win32".  This might be a better answer than
using native w32 threading we now use because we could better focus on
just the pthread coding model and reduce complexity in the thread class.

I have also looked at producing am experimental variant of common c++,
perhaps to be called "embedded common c++", which basically builds
around the notion of -nostdlib and hence no c++ standard library.  We
often have embedded projects which would greatly benefit from c++ for
design, but rely exclusively on c coded libraries, and perhaps are on
targets which cannot support the huge and duplicative stdc++ library and
it's template generated code, exceptions, etc.  The idea is to have a
object oriented framework for developing embedded services which adds no
real overhead to support compared to using pure C.

We will likely not break most existing common c++ based code, since many
of the existing classes and behaviors will still also exist.  Some
things will disappear however, including the current Pointer template (a
new RefPointer that behaves the same but is constructed like the new
pointer will be used instead) and the current objxxx templates which I
do not believe anyone uses.  If we consolidate around the pthread
threading model, the thread suspend/resume support will be eliminated,
since there was no real way to simulate this on most pthread platforms
anyway.  Cancelable threads based designs will in any case benefit from
the new auto_release mechanism.

One area I might restructure is the dso support, perhaps introducing a
dlfcn compatibility wrapper for w32 and using the posix shared object
support functions directly rather than a class wrapper.  Some of the
crufty file classes may also be killed or cleaned up.

One area with a very large potential for change is Socket.   Perhaps it
would be better if "Address" became a struct sockaddr rather than a base
IPV4 socket address (and separate AddressIPV6 classes/methods).  This I
know would break a lot of existing things, but would simplify many as well.

--------------000600000505010906070109
Content-Type: text/x-vcard; charset=utf-8;
 name="dyfet.vcf"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
 filename="dyfet.vcf"

YmVnaW46dmNhcmQNCmZuOkRhdmlkIFN1Z2FyDQpuOlN1Z2FyO0RhdmlkDQpvcmc6R05VIFRl
bGVwaG9ueQ0KZW1haWw7aW50ZXJuZXQ6ZHlmZXRAZ251dGVsZXBob255Lm9yZw0KdGVsO3dv
cms6KzEgMjAxIDIxNSAyNjA5DQp1cmw6aHR0cDovL3d3dy5nbnV0ZWxlcGhvbnkub3JnDQp2
ZXJzaW9uOjIuMQ0KZW5kOnZjYXJkDQoNCg==
--------------000600000505010906070109--



From MAILER-DAEMON Sun Jan 28 12:55:43 2007
Received: from mailman by lists.gnu.org with archive (Exim 4.43)
	id 1HBEFj-0003pN-HI
	for mharc-bug-commoncpp@gnu.org; Sun, 28 Jan 2007 12:55:43 -0500
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1HBEFi-0003pI-23
	for bug-commoncpp@gnu.org; Sun, 28 Jan 2007 12:55:42 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1HBEFg-0003p6-Dt
	for bug-commoncpp@gnu.org; Sun, 28 Jan 2007 12:55:40 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1HBEFg-0003p3-9c
	for bug-commoncpp@gnu.org; Sun, 28 Jan 2007 12:55:40 -0500
Received: from host79-17-static.37-85-b.business.telecomitalia.it
	([85.37.17.79] helo=MTA079C.interbusiness.it)
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1HBEFf-0007DF-K1
	for bug-commoncpp@gnu.org; Sun, 28 Jan 2007 12:55:40 -0500
Received: from host123-160-static.29-87-b.business.telecomitalia.it (HELO
	[192.168.0.1]) ([87.29.160.123])
	by MTA079C.interbusiness.it with ESMTP; 28 Jan 2007 18:55:35 +0100
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAAEJyvEVXHaB7/2dsb2JhbAANgwA3iAGBYA
Message-ID: <45BCE39B.10408@bigfoot.com>
Date: Sun, 28 Jan 2007 18:55:39 +0100
From: Wakan <wakan@bigfoot.com>
User-Agent: Mozilla Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: David Sugar <dyfet@gnutelephony.org>
References: <NBBBKGBBDBMONCPMINHBMEBDLGAB.Conrad@Pino.com>
	<45BBC29A.8060608@gnutelephony.org>
In-Reply-To: <45BBC29A.8060608@gnutelephony.org>
Content-Type: text/html; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit
X-detected-kernel: FreeBSD 2.0-4.2
Cc: bug-commoncpp@gnu.org, "Conrad T. Pino" <Conrad@Pino.com>
Subject: Re: can't release mutex
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/bug-commoncpp>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Jan 2007 17:55:42 -0000

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-15"
 http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Thanks for your reply.<br>
Can you write an example with the semaphore in this context?<br>
Thanks,<br>
Carlo<br>
<br>
David Sugar ha scritto:
<blockquote cite="mid45BBC29A.8060608@gnutelephony.org" type="cite">
  <pre wrap="">I think what he really wants to do is use the Common C++ Semaphore with
a count of 1, since semaphore can block with a "timeout", and with a "1"
count in effect acts as a mutex...

The larger question though of what to do with the stuck thread, perhaps
from a broken library, is important also.  He could cancel the thread in
question if it timed out, and put cleanup code in the thread destructor
when he invokes delete to join it, but if the library allocated
resources he cannot determine for them to get cleanly deallocated.

Conrad T. Pino wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">You're on the right track.  Please pardon my rusty recollection syntax.
Revise:

	mutex.enterMutex();

to a form that accepts a timeout.  This example won't compile:

	const int timeout = 500;

	while (1) {
		if ( isPending( pendingInput ) ) {
			int result = mutex.enterMutex( timeout );

			if ( result == success ) {
				---&gt; protected function call (a function that can't work 
				in multithread env) &lt;---       
				mutex.leaveMutex();
			} else {
				// do something else with pending input
			}
		}
	}

While the above will implement your timeout idea it does nothing about
the fundamental problem.  When the library "breaks" can be discoverd
and the blocked mutex/thread combination can be cancelled/restared
HOWEVER PROPRIETARY LIBRARY STATE IS INCONSISTENT &amp; LIKELY DANGEROUS.

If the library is dynamically loaded under your control then unload it
and reload it to get it back into a consistent state.  If it's auto or
static linked then you may have an unsolveable problem.

If a reliable system is your goal then one of these MUST be true:

		proprietary library NEVER fails
	OR
		proprietary library can be forced back to a consistent
		state because it has a reload or reinitialize method

Good luck.

    </pre>
    <blockquote type="cite">
      <pre wrap="">-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:bug-commoncpp-bounces+conrad=pino.com@gnu.org">bug-commoncpp-bounces+conrad=pino.com@gnu.org</a>
[<a class="moz-txt-link-freetext" href="mailto:bug-commoncpp-bounces+conrad=pino.com@gnu.org">mailto:bug-commoncpp-bounces+conrad=pino.com@gnu.org</a>]On Behalf Of Wakan
Sent: Saturday, January 27, 2007 07:18
To: <a class="moz-txt-link-abbreviated" href="mailto:bug-commoncpp@gnu.org">bug-commoncpp@gnu.org</a>
Subject: can't release mutex

Hi,
I'm using commoncpp library in a project that includes a multithread 
server that
can accept many tcp connection and each connection generates a thread.
In this server I'm using a thirdy party proprietary library (compiled), 
that (as the producer says)
can't work in multithread environment.
As each connection thread needs to call functions of this thirdy party 
library, I've used a mutex to protect the piece of
code where this external library function is called.
In this way I can use this library fine, because all calls are 
serialized and the protected function is called by one thread each time.
This is an example:
...
    while(1) {
        if(isPending(pendingInput)) {
                mutex.enterMutex();
                ---&gt; protected function call (a function that can't work 
in multithread env) &lt;---       
                mutex.leaveMutex();
       }
    }
...
in 99% of cases it works fine. But it accidentally happens that a thread 
can't exit from the mutex
maybe because the thirdy party function freezes itself.
When this happens, the server can accept other connections, soit still 
works, but each thread can't enter in the mutex proteced piece of code.
I'm thinking about something, like a timeout, that exits the mutex after 
a time, if the thread is not exiting...
Can someone help me to resolve this problem? Are there other solutions?
Thanks in advance,
Regards
Carlo
      </pre>
    </blockquote>
    <pre wrap="">

_______________________________________________
Bug-commoncpp mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Bug-commoncpp@gnu.org">Bug-commoncpp@gnu.org</a>
<a class="moz-txt-link-freetext" href="http://lists.gnu.org/mailman/listinfo/bug-commoncpp">http://lists.gnu.org/mailman/listinfo/bug-commoncpp</a>
    </pre>
  </blockquote>
  <pre wrap=""><!---->

__________ NOD32 2011 (20070127) Information __________

This message was checked by NOD32 antivirus system.
<a class="moz-txt-link-freetext" href="http://www.eset.com">http://www.eset.com</a>

  </pre>
</blockquote>
<br>
</body>
</html>



From MAILER-DAEMON Sun Jan 28 14:06:34 2007
Received: from mailman by lists.gnu.org with archive (Exim 4.43)
	id 1HBFMI-00064p-2C
	for mharc-bug-commoncpp@gnu.org; Sun, 28 Jan 2007 14:06:34 -0500
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1HBFMG-00064k-Qk
	for bug-commoncpp@gnu.org; Sun, 28 Jan 2007 14:06:32 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1HBFMF-00064Y-7I
	for bug-commoncpp@gnu.org; Sun, 28 Jan 2007 14:06:31 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1HBFMF-00064V-2L
	for bug-commoncpp@gnu.org; Sun, 28 Jan 2007 14:06:31 -0500
Received: from host64-17-static.37-85-b.business.telecomitalia.it
	([85.37.17.64] helo=MTA064B.interbusiness.it)
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1HBFME-0000pJ-5A
	for bug-commoncpp@gnu.org; Sun, 28 Jan 2007 14:06:30 -0500
Received: from host123-160-static.29-87-b.business.telecomitalia.it (HELO
	[192.168.0.1]) ([87.29.160.123])
	by MTA064B.interbusiness.it with ESMTP; 28 Jan 2007 20:06:27 +0100
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAAAH6CvEVXHaB7/2dsb2JhbAANgwA3iAGBYA
Message-ID: <45BCF437.4050100@bigfoot.com>
Date: Sun, 28 Jan 2007 20:06:31 +0100
From: Wakan <wakan@bigfoot.com>
User-Agent: Mozilla Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: Wakan <wakan@bigfoot.com>
References: <NBBBKGBBDBMONCPMINHBMEBDLGAB.Conrad@Pino.com>	<45BBC29A.8060608@gnutelephony.org>
	<45BCE39B.10408@bigfoot.com>
In-Reply-To: <45BCE39B.10408@bigfoot.com>
Content-Type: text/html; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit
X-detected-kernel: FreeBSD 2.0-4.2
Cc: David Sugar <dyfet@gnutelephony.org>, bug-commoncpp@gnu.org,
	"Conrad T. Pino" <Conrad@Pino.com>
Subject: Re: can't release mutex
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/bug-commoncpp>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Jan 2007 19:06:32 -0000

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-15"
 http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Thanks for your reply.<br>
Can you write an example with the semaphore in this context?<br>
Thanks,<br>
Carlo<br>
<br>
Wakan ha scritto:
<blockquote cite="mid45BCE39B.10408@bigfoot.com" type="cite">
  <meta content="text/html;charset=ISO-8859-15"
 http-equiv="Content-Type">
Thanks for your reply.<br>
Can you write an example with the semaphore in this context?<br>
Thanks,<br>
Carlo<br>
  <br>
David Sugar ha scritto:
  <blockquote cite="mid45BBC29A.8060608@gnutelephony.org" type="cite">
    <pre wrap="">I think what he really wants to do is use the Common C++ Semaphore with
a count of 1, since semaphore can block with a "timeout", and with a "1"
count in effect acts as a mutex...

The larger question though of what to do with the stuck thread, perhaps
from a broken library, is important also.  He could cancel the thread in
question if it timed out, and put cleanup code in the thread destructor
when he invokes delete to join it, but if the library allocated
resources he cannot determine for them to get cleanly deallocated.

Conrad T. Pino wrote:
  </pre>
    <blockquote type="cite">
      <pre wrap="">You're on the right track.  Please pardon my rusty recollection syntax.
Revise:

	mutex.enterMutex();

to a form that accepts a timeout.  This example won't compile:

	const int timeout = 500;

	while (1) {
		if ( isPending( pendingInput ) ) {
			int result = mutex.enterMutex( timeout );

			if ( result == success ) {
				---&gt; protected function call (a function that can't work 
				in multithread env) &lt;---       
				mutex.leaveMutex();
			} else {
				// do something else with pending input
			}
		}
	}

While the above will implement your timeout idea it does nothing about
the fundamental problem.  When the library "breaks" can be discoverd
and the blocked mutex/thread combination can be cancelled/restared
HOWEVER PROPRIETARY LIBRARY STATE IS INCONSISTENT &amp; LIKELY DANGEROUS.

If the library is dynamically loaded under your control then unload it
and reload it to get it back into a consistent state.  If it's auto or
static linked then you may have an unsolveable problem.

If a reliable system is your goal then one of these MUST be true:

		proprietary library NEVER fails
	OR
		proprietary library can be forced back to a consistent
		state because it has a reload or reinitialize method

Good luck.

    </pre>
      <blockquote type="cite">
        <pre wrap="">-----Original Message-----
From: <a class="moz-txt-link-abbreviated"
 href="mailto:bug-commoncpp-bounces+conrad=pino.com@gnu.org">bug-commoncpp-bounces+conrad=pino.com@gnu.org</a>
[<a class="moz-txt-link-freetext"
 href="mailto:bug-commoncpp-bounces+conrad=pino.com@gnu.org">mailto:bug-commoncpp-bounces+conrad=pino.com@gnu.org</a>]On Behalf Of Wakan
Sent: Saturday, January 27, 2007 07:18
To: <a class="moz-txt-link-abbreviated"
 href="mailto:bug-commoncpp@gnu.org">bug-commoncpp@gnu.org</a>
Subject: can't release mutex

Hi,
I'm using commoncpp library in a project that includes a multithread 
server that
can accept many tcp connection and each connection generates a thread.
In this server I'm using a thirdy party proprietary library (compiled), 
that (as the producer says)
can't work in multithread environment.
As each connection thread needs to call functions of this thirdy party 
library, I've used a mutex to protect the piece of
code where this external library function is called.
In this way I can use this library fine, because all calls are 
serialized and the protected function is called by one thread each time.
This is an example:
...
    while(1) {
        if(isPending(pendingInput)) {
                mutex.enterMutex();
                ---&gt; protected function call (a function that can't work 
in multithread env) &lt;---       
                mutex.leaveMutex();
       }
    }
...
in 99% of cases it works fine. But it accidentally happens that a thread 
can't exit from the mutex
maybe because the thirdy party function freezes itself.
When this happens, the server can accept other connections, soit still 
works, but each thread can't enter in the mutex proteced piece of code.
I'm thinking about something, like a timeout, that exits the mutex after 
a time, if the thread is not exiting...
Can someone help me to resolve this problem? Are there other solutions?
Thanks in advance,
Regards
Carlo
      </pre>
      </blockquote>
      <pre wrap="">
_______________________________________________
Bug-commoncpp mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Bug-commoncpp@gnu.org">Bug-commoncpp@gnu.org</a>
<a class="moz-txt-link-freetext"
 href="http://lists.gnu.org/mailman/listinfo/bug-commoncpp">http://lists.gnu.org/mailman/listinfo/bug-commoncpp</a>
    </pre>
    </blockquote>
    <pre wrap=""><!---->

__________ NOD32 2011 (20070127) Information __________

This message was checked by NOD32 antivirus system.
<a class="moz-txt-link-freetext" href="http://www.eset.com">http://www.eset.com</a>

  </pre>
  </blockquote>
  <br>
  <br>
  <br>
__________ NOD32 2014 (20070128) Information __________<br>
  <br>
This message was checked by NOD32 antivirus system.<br>
  <a href="http://www.eset.com">http://www.eset.com</a><br>
  <pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Bug-commoncpp mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Bug-commoncpp@gnu.org">Bug-commoncpp@gnu.org</a>
<a class="moz-txt-link-freetext" href="http://lists.gnu.org/mailman/listinfo/bug-commoncpp">http://lists.gnu.org/mailman/listinfo/bug-commoncpp</a>


__________ NOD32 2014 (20070128) Information __________

This message was checked by NOD32 antivirus system.
<a class="moz-txt-link-freetext" href="http://www.eset.com">http://www.eset.com</a>

  </pre>
</blockquote>
<br>
</body>
</html>



From MAILER-DAEMON Sun Jan 28 14:27:50 2007
Received: from mailman by lists.gnu.org with archive (Exim 4.43)
	id 1HBFgr-00067a-RW
	for mharc-bug-commoncpp@gnu.org; Sun, 28 Jan 2007 14:27:49 -0500
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1HBFgp-00064n-Uh
	for bug-commoncpp@gnu.org; Sun, 28 Jan 2007 14:27:48 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1HBFgo-00062k-Is
	for bug-commoncpp@gnu.org; Sun, 28 Jan 2007 14:27:46 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1HBFgo-00062h-DR
	for bug-commoncpp@gnu.org; Sun, 28 Jan 2007 14:27:46 -0500
Received: from outbound.mailhop.org ([63.208.196.171])
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1HBFgo-0004Pg-3B
	for bug-commoncpp@gnu.org; Sun, 28 Jan 2007 14:27:46 -0500
Received: from pool-72-76-21-88.nwrknj.fios.verizon.net ([72.76.21.88]
	helo=[192.168.1.90])
	by outbound.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256)
	(Exim 4.63) (envelope-from <dyfet@gnutelephony.org>)
	id 1HBFgn-000BhR-8f; Sun, 28 Jan 2007 14:27:45 -0500
X-Mail-Handler: MailHop Outbound by DynDNS
X-Originating-IP: 72.76.21.88
X-Report-Abuse-To: abuse@dyndns.com (see
	http://www.mailhop.org/outbound/abuse.html for abuse reporting
	information)
X-MHO-User: dyfet
Message-ID: <45BCF930.6010904@gnutelephony.org>
Date: Sun, 28 Jan 2007 14:27:44 -0500
From: David Sugar <dyfet@gnutelephony.org>
User-Agent: Thunderbird 1.5.0.9 (X11/20061219)
MIME-Version: 1.0
To: Wakan <wakan@bigfoot.com>
References: <NBBBKGBBDBMONCPMINHBMEBDLGAB.Conrad@Pino.com>
	<45BBC29A.8060608@gnutelephony.org>
	<45BCE39B.10408@bigfoot.com> <45BCF437.4050100@bigfoot.com>
In-Reply-To: <45BCF437.4050100@bigfoot.com>
X-Enigmail-Version: 0.94.0.0
Content-Type: multipart/mixed; boundary="------------070908030809070302070700"
X-detected-kernel: FreeBSD 4.6-4.9
Cc: bug-commoncpp@gnu.org, "Conrad T. Pino" <Conrad@Pino.com>
Subject: Re: can't release mutex
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/bug-commoncpp>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Jan 2007 19:27:48 -0000

This is a multi-part message in MIME format.
--------------070908030809070302070700
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit

What you are thinking of is something like this:

	Semaphore semimutex(1);

	...
	if(isPending(pendingInput)) {
		if(!semimutex.wait(timeout)) {
			library must have crashed, etc...
		}
		call library function ...
		semimutex.post();
	}

Hence wait is used like a enterMutex, post like a leaveMutex, and only
one instance can pass through because it has a count of 1.  Since wait
supports a timeout, you can use that for your failure detect.

The Common C++ Semaphore is actually implemented as a combination of
mutex and a conditional.

Wakan wrote:
> Thanks for your reply.
> Can you write an example with the semaphore in this context?
> Thanks,
> Carlo
> 
> Wakan ha scritto:
>> Thanks for your reply.
>> Can you write an example with the semaphore in this context?
>> Thanks,
>> Carlo
>>
>> David Sugar ha scritto:
>>> I think what he really wants to do is use the Common C++ Semaphore with
>>> a count of 1, since semaphore can block with a "timeout", and with a "1"
>>> count in effect acts as a mutex...
>>>
>>> The larger question though of what to do with the stuck thread, perhaps
>>> from a broken library, is important also.  He could cancel the thread in
>>> question if it timed out, and put cleanup code in the thread destructor
>>> when he invokes delete to join it, but if the library allocated
>>> resources he cannot determine for them to get cleanly deallocated.
>>>
>>> Conrad T. Pino wrote:
>>>   
>>>> You're on the right track.  Please pardon my rusty recollection syntax.
>>>> Revise:
>>>>
>>>> 	mutex.enterMutex();
>>>>
>>>> to a form that accepts a timeout.  This example won't compile:
>>>>
>>>> 	const int timeout = 500;
>>>>
>>>> 	while (1) {
>>>> 		if ( isPending( pendingInput ) ) {
>>>> 			int result = mutex.enterMutex( timeout );
>>>>
>>>> 			if ( result == success ) {
>>>> 				---> protected function call (a function that can't work 
>>>> 				in multithread env) <---       
>>>> 				mutex.leaveMutex();
>>>> 			} else {
>>>> 				// do something else with pending input
>>>> 			}
>>>> 		}
>>>> 	}
>>>>
>>>> While the above will implement your timeout idea it does nothing about
>>>> the fundamental problem.  When the library "breaks" can be discoverd
>>>> and the blocked mutex/thread combination can be cancelled/restared
>>>> HOWEVER PROPRIETARY LIBRARY STATE IS INCONSISTENT & LIKELY DANGEROUS.
>>>>
>>>> If the library is dynamically loaded under your control then unload it
>>>> and reload it to get it back into a consistent state.  If it's auto or
>>>> static linked then you may have an unsolveable problem.
>>>>
>>>> If a reliable system is your goal then one of these MUST be true:
>>>>
>>>> 		proprietary library NEVER fails
>>>> 	OR
>>>> 		proprietary library can be forced back to a consistent
>>>> 		state because it has a reload or reinitialize method
>>>>
>>>> Good luck.
>>>>
>>>>     
>>>>> -----Original Message-----
>>>>> From: bug-commoncpp-bounces+conrad=pino.com@gnu.org
>>>>> [mailto:bug-commoncpp-bounces+conrad=pino.com@gnu.org]On Behalf Of Wakan
>>>>> Sent: Saturday, January 27, 2007 07:18
>>>>> To: bug-commoncpp@gnu.org
>>>>> Subject: can't release mutex
>>>>>
>>>>> Hi,
>>>>> I'm using commoncpp library in a project that includes a multithread 
>>>>> server that
>>>>> can accept many tcp connection and each connection generates a thread.
>>>>> In this server I'm using a thirdy party proprietary library (compiled), 
>>>>> that (as the producer says)
>>>>> can't work in multithread environment.
>>>>> As each connection thread needs to call functions of this thirdy party 
>>>>> library, I've used a mutex to protect the piece of
>>>>> code where this external library function is called.
>>>>> In this way I can use this library fine, because all calls are 
>>>>> serialized and the protected function is called by one thread each time.
>>>>> This is an example:
>>>>> ...
>>>>>     while(1) {
>>>>>         if(isPending(pendingInput)) {
>>>>>                 mutex.enterMutex();
>>>>>                 ---> protected function call (a function that can't work 
>>>>> in multithread env) <---       
>>>>>                 mutex.leaveMutex();
>>>>>        }
>>>>>     }
>>>>> ...
>>>>> in 99% of cases it works fine. But it accidentally happens that a thread 
>>>>> can't exit from the mutex
>>>>> maybe because the thirdy party function freezes itself.
>>>>> When this happens, the server can accept other connections, soit still 
>>>>> works, but each thread can't enter in the mutex proteced piece of code.
>>>>> I'm thinking about something, like a timeout, that exits the mutex after 
>>>>> a time, if the thread is not exiting...
>>>>> Can someone help me to resolve this problem? Are there other solutions?
>>>>> Thanks in advance,
>>>>> Regards
>>>>> Carlo
>>>>>       
>>>> _______________________________________________
>>>> Bug-commoncpp mailing list
>>>> Bug-commoncpp@gnu.org
>>>> http://lists.gnu.org/mailman/listinfo/bug-commoncpp
>>>>     
>>>
>>>
>>> __________ NOD32 2011 (20070127) Information __________
>>>
>>> This message was checked by NOD32 antivirus system.
>>> http://www.eset.com
>>>
>>>   
>>
>>
>>
>> __________ NOD32 2014 (20070128) Information __________
>>
>> This message was checked by NOD32 antivirus system.
>> http://www.eset.com
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Bug-commoncpp mailing list
>> Bug-commoncpp@gnu.org
>> http://lists.gnu.org/mailman/listinfo/bug-commoncpp
>>
>>
>> __________ NOD32 2014 (20070128) Information __________
>>
>> This message was checked by NOD32 antivirus system.
>> http://www.eset.com
>>
>>   
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://lists.gnu.org/mailman/listinfo/bug-commoncpp

--------------070908030809070302070700
Content-Type: text/x-vcard; charset=utf-8;
 name="dyfet.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="dyfet.vcf"

begin:vcard
fn:David Sugar
n:Sugar;David
org:GNU Telephony
email;internet:dyfet@gnutelephony.org
tel;work:+1 201 215 2609
url:http://www.gnutelephony.org
version:2.1
end:vcard


--------------070908030809070302070700--



From MAILER-DAEMON Sun Jan 28 15:32:17 2007
Received: from mailman by lists.gnu.org with archive (Exim 4.43)
	id 1HBGhE-0007An-VI
	for mharc-bug-commoncpp@gnu.org; Sun, 28 Jan 2007 15:32:17 -0500
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1HBGhC-0007AI-DI
	for bug-commoncpp@gnu.org; Sun, 28 Jan 2007 15:32:14 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1HBGhB-0007A5-F4
	for bug-commoncpp@gnu.org; Sun, 28 Jan 2007 15:32:13 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1HBGhB-0007A2-9q
	for bug-commoncpp@gnu.org; Sun, 28 Jan 2007 15:32:13 -0500
Received: from host64-17-static.37-85-b.business.telecomitalia.it
	([85.37.17.64] helo=MTA064B.interbusiness.it)
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1HBGhA-0007zm-CS
	for bug-commoncpp@gnu.org; Sun, 28 Jan 2007 15:32:13 -0500
Received: from host123-160-static.29-87-b.business.telecomitalia.it (HELO
	[192.168.0.1]) ([87.29.160.123])
	by MTA064B.interbusiness.it with ESMTP; 28 Jan 2007 21:32:10 +0100
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CANKWvEVXHaB7/2dsb2JhbAANgwA3K4dVgWA
Message-ID: <45BD084F.5080603@bigfoot.com>
Date: Sun, 28 Jan 2007 21:32:15 +0100
From: Wakan <wakan@bigfoot.com>
User-Agent: Mozilla Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: David Sugar <dyfet@gnutelephony.org>
References: <NBBBKGBBDBMONCPMINHBMEBDLGAB.Conrad@Pino.com>
	<45BBC29A.8060608@gnutelephony.org>
	<45BCE39B.10408@bigfoot.com> <45BCF437.4050100@bigfoot.com>
	<45BCF930.6010904@gnutelephony.org>
In-Reply-To: <45BCF930.6010904@gnutelephony.org>
Content-Type: text/html; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit
X-detected-kernel: FreeBSD 2.0-4.2
Cc: bug-commoncpp@gnu.org, "Conrad T. Pino" <Conrad@Pino.com>
Subject: Re: can't release mutex
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/bug-commoncpp>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Jan 2007 20:32:14 -0000

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-15"
 http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
OK David,<br>
first of all thanks for your precious help...<br>
only a clarifying question (clarifying for me of course... :)):<br>
<br>
when the library function execution exceeds the timeout value, <br>
the piece of code in: <br>
<pre wrap="">		if(!semimutex.wait(timeout)) {
	----------&gt; library must have crashed, etc...
		}
</pre>
runs automatically? That is: is there a sort of "goto" that let the
execution continue within the<br>
if statement? I put this question because (besides my ignorance), if I
have to put an external loop that checks for the<br>
timeout, like...<br>
<pre wrap="">	if(isPending(pendingInput)) {
	---&gt;	while(1) {
			if(!semimutex.wait(timeout)) {
				library must have crashed, etc...
			}
			call library function ...
			semimutex.post();
		}
	}
</pre>
it probably won't resolve my problem, because when external library get
stucked, the program can't go on,<br>
and never will reach the beginning of the external loop, never will
excute the piece of code of the timeout condition.<br>
If there is an automatic "goto" instead, then I think it will work fine.<br>
<br>
And more, in this way I can implement a sort of "time sharing", because
even if my server is multithread, actually only 1 thread can execute
until<br>
the library function exits (it isn't a fix execution time), so it's a
fake multithread and performance speed is heavily penalized indeed. <br>
To have this working, I have to increase the couter of the semaphore?
Can you make other example of the semaphore usage please? <br>
or suggest some documentation to read about this?<br>
<br>
Thanks again for your help.<br>
Carlo<br>
<br>
<br>
David Sugar ha scritto:
<blockquote cite="mid45BCF930.6010904@gnutelephony.org" type="cite">
  <pre wrap="">What you are thinking of is something like this:

	Semaphore semimutex(1);

	...
	if(isPending(pendingInput)) {
		if(!semimutex.wait(timeout)) {
			library must have crashed, etc...
		}
		call library function ...
		semimutex.post();
	}

Hence wait is used like a enterMutex, post like a leaveMutex, and only
one instance can pass through because it has a count of 1.  Since wait
supports a timeout, you can use that for your failure detect.

The Common C++ Semaphore is actually implemented as a combination of
mutex and a conditional.

Wakan wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">Thanks for your reply.
Can you write an example with the semaphore in this context?
Thanks,
Carlo

Wakan ha scritto:
    </pre>
    <blockquote type="cite">
      <pre wrap="">Thanks for your reply.
Can you write an example with the semaphore in this context?
Thanks,
Carlo

David Sugar ha scritto:
      </pre>
      <blockquote type="cite">
        <pre wrap="">I think what he really wants to do is use the Common C++ Semaphore with
a count of 1, since semaphore can block with a "timeout", and with a "1"
count in effect acts as a mutex...

The larger question though of what to do with the stuck thread, perhaps
from a broken library, is important also.  He could cancel the thread in
question if it timed out, and put cleanup code in the thread destructor
when he invokes delete to join it, but if the library allocated
resources he cannot determine for them to get cleanly deallocated.

Conrad T. Pino wrote:
  
        </pre>
        <blockquote type="cite">
          <pre wrap="">You're on the right track.  Please pardon my rusty recollection syntax.
Revise:

	mutex.enterMutex();

to a form that accepts a timeout.  This example won't compile:

	const int timeout = 500;

	while (1) {
		if ( isPending( pendingInput ) ) {
			int result = mutex.enterMutex( timeout );

			if ( result == success ) {
				---&gt; protected function call (a function that can't work 
				in multithread env) &lt;---       
				mutex.leaveMutex();
			} else {
				// do something else with pending input
			}
		}
	}

While the above will implement your timeout idea it does nothing about
the fundamental problem.  When the library "breaks" can be discoverd
and the blocked mutex/thread combination can be cancelled/restared
HOWEVER PROPRIETARY LIBRARY STATE IS INCONSISTENT &amp; LIKELY DANGEROUS.

If the library is dynamically loaded under your control then unload it
and reload it to get it back into a consistent state.  If it's auto or
static linked then you may have an unsolveable problem.

If a reliable system is your goal then one of these MUST be true:

		proprietary library NEVER fails
	OR
		proprietary library can be forced back to a consistent
		state because it has a reload or reinitialize method

Good luck.

    
          </pre>
          <blockquote type="cite">
            <pre wrap="">-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:bug-commoncpp-bounces+conrad=pino.com@gnu.org">bug-commoncpp-bounces+conrad=pino.com@gnu.org</a>
[<a class="moz-txt-link-freetext" href="mailto:bug-commoncpp-bounces+conrad=pino.com@gnu.org">mailto:bug-commoncpp-bounces+conrad=pino.com@gnu.org</a>]On Behalf Of Wakan
Sent: Saturday, January 27, 2007 07:18
To: <a class="moz-txt-link-abbreviated" href="mailto:bug-commoncpp@gnu.org">bug-commoncpp@gnu.org</a>
Subject: can't release mutex

Hi,
I'm using commoncpp library in a project that includes a multithread 
server that
can accept many tcp connection and each connection generates a thread.
In this server I'm using a thirdy party proprietary library (compiled), 
that (as the producer says)
can't work in multithread environment.
As each connection thread needs to call functions of this thirdy party 
library, I've used a mutex to protect the piece of
code where this external library function is called.
In this way I can use this library fine, because all calls are 
serialized and the protected function is called by one thread each time.
This is an example:
...
    while(1) {
        if(isPending(pendingInput)) {
                mutex.enterMutex();
                ---&gt; protected function call (a function that can't work 
in multithread env) &lt;---       
                mutex.leaveMutex();
       }
    }
...
in 99% of cases it works fine. But it accidentally happens that a thread 
can't exit from the mutex
maybe because the thirdy party function freezes itself.
When this happens, the server can accept other connections, soit still 
works, but each thread can't enter in the mutex proteced piece of code.
I'm thinking about something, like a timeout, that exits the mutex after 
a time, if the thread is not exiting...
Can someone help me to resolve this problem? Are there other solutions?
Thanks in advance,
Regards
Carlo
      
            </pre>
          </blockquote>
          <pre wrap="">_______________________________________________
Bug-commoncpp mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Bug-commoncpp@gnu.org">Bug-commoncpp@gnu.org</a>
<a class="moz-txt-link-freetext" href="http://lists.gnu.org/mailman/listinfo/bug-commoncpp">http://lists.gnu.org/mailman/listinfo/bug-commoncpp</a>
    
          </pre>
        </blockquote>
        <pre wrap="">
__________ NOD32 2011 (20070127) Information __________

This message was checked by NOD32 antivirus system.
<a class="moz-txt-link-freetext" href="http://www.eset.com">http://www.eset.com</a>

  
        </pre>
      </blockquote>
      <pre wrap="">

__________ NOD32 2014 (20070128) Information __________

This message was checked by NOD32 antivirus system.
<a class="moz-txt-link-freetext" href="http://www.eset.com">http://www.eset.com</a>
------------------------------------------------------------------------

_______________________________________________
Bug-commoncpp mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Bug-commoncpp@gnu.org">Bug-commoncpp@gnu.org</a>
<a class="moz-txt-link-freetext" href="http://lists.gnu.org/mailman/listinfo/bug-commoncpp">http://lists.gnu.org/mailman/listinfo/bug-commoncpp</a>


__________ NOD32 2014 (20070128) Information __________

This message was checked by NOD32 antivirus system.
<a class="moz-txt-link-freetext" href="http://www.eset.com">http://www.eset.com</a>

  
      </pre>
    </blockquote>
    <pre wrap="">
------------------------------------------------------------------------

_______________________________________________
Bug-commoncpp mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Bug-commoncpp@gnu.org">Bug-commoncpp@gnu.org</a>
<a class="moz-txt-link-freetext" href="http://lists.gnu.org/mailman/listinfo/bug-commoncpp">http://lists.gnu.org/mailman/listinfo/bug-commoncpp</a>
    </pre>
  </blockquote>
  <pre wrap=""><!---->

__________ NOD32 2014 (20070128) Information __________

This message was checked by NOD32 antivirus system.
<a class="moz-txt-link-freetext" href="http://www.eset.com">http://www.eset.com</a>

  </pre>
</blockquote>
<br>
</body>
</html>



From MAILER-DAEMON Sun Jan 28 18:31:52 2007
Received: from mailman by lists.gnu.org with archive (Exim 4.43)
	id 1HBJV2-00067Z-8x
	for mharc-bug-commoncpp@gnu.org; Sun, 28 Jan 2007 18:31:52 -0500
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1HBJV1-00067U-6c
	for bug-commoncpp@gnu.org; Sun, 28 Jan 2007 18:31:51 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1HBJUy-00067I-37
	for bug-commoncpp@gnu.org; Sun, 28 Jan 2007 18:31:49 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1HBJUx-00067F-UG
	for bug-commoncpp@gnu.org; Sun, 28 Jan 2007 18:31:47 -0500
Received: from outbound.mailhop.org ([63.208.196.171])
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1HBJUx-0002d2-E2
	for bug-commoncpp@gnu.org; Sun, 28 Jan 2007 18:31:47 -0500
Received: from pool-72-76-21-88.nwrknj.fios.verizon.net ([72.76.21.88]
	helo=[192.168.1.90])
	by outbound.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256)
	(Exim 4.63) (envelope-from <dyfet@gnutelephony.org>)
	id 1HBJUw-000AMw-BE; Sun, 28 Jan 2007 18:31:46 -0500
X-Mail-Handler: MailHop Outbound by DynDNS
X-Originating-IP: 72.76.21.88
X-Report-Abuse-To: abuse@dyndns.com (see
	http://www.mailhop.org/outbound/abuse.html for abuse reporting
	information)
X-MHO-User: dyfet
Message-ID: <45BD3261.6000903@gnutelephony.org>
Date: Sun, 28 Jan 2007 18:31:45 -0500
From: David Sugar <dyfet@gnutelephony.org>
User-Agent: Thunderbird 1.5.0.9 (X11/20061219)
MIME-Version: 1.0
To: Wakan <wakan@bigfoot.com>
References: <NBBBKGBBDBMONCPMINHBMEBDLGAB.Conrad@Pino.com>
	<45BBC29A.8060608@gnutelephony.org>
	<45BCE39B.10408@bigfoot.com> <45BCF437.4050100@bigfoot.com>
	<45BCF930.6010904@gnutelephony.org> <45BD084F.5080603@bigfoot.com>
In-Reply-To: <45BD084F.5080603@bigfoot.com>
X-Enigmail-Version: 0.94.0.0
Content-Type: multipart/mixed; boundary="------------060402090703080509050309"
X-detected-kernel: FreeBSD 4.6-4.9
Cc: bug-commoncpp@gnu.org, "Conrad T. Pino" <Conrad@Pino.com>
Subject: Re: can't release mutex
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/bug-commoncpp>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 28 Jan 2007 23:31:51 -0000

This is a multi-part message in MIME format.
--------------060402090703080509050309
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit

No, any OTHER thread that would have blocked on that lock will continue
after the timeout...so if you are using a common lock, you want another
thread to hit it, and use the wait to enter, as it can then see if the
lock got stuck, while your processing thread does so without a timeout....


Wakan wrote:
> OK David,
> first of all thanks for your precious help...
> only a clarifying question (clarifying for me of course... :)):
> 
> when the library function execution exceeds the timeout value,
> the piece of code in:
> 
> 		if(!semimutex.wait(timeout)) {
> 	----------> library must have crashed, etc...
> 		}
> 
> runs automatically? That is: is there a sort of "goto" that let the
> execution continue within the
> if statement? I put this question because (besides my ignorance), if I
> have to put an external loop that checks for the
> timeout, like...
> 
> 	if(isPending(pendingInput)) {
> 	--->	while(1) {
> 			if(!semimutex.wait(timeout)) {
> 				library must have crashed, etc...
> 			}
> 			call library function ...
> 			semimutex.post();
> 		}
> 	}
> 
> it probably won't resolve my problem, because when external library get
> stucked, the program can't go on,
> and never will reach the beginning of the external loop, never will
> excute the piece of code of the timeout condition.
> If there is an automatic "goto" instead, then I think it will work fine.
> 
> And more, in this way I can implement a sort of "time sharing", because
> even if my server is multithread, actually only 1 thread can execute until
> the library function exits (it isn't a fix execution time), so it's a
> fake multithread and performance speed is heavily penalized indeed.
> To have this working, I have to increase the couter of the semaphore?
> Can you make other example of the semaphore usage please?
> or suggest some documentation to read about this?
> 
> Thanks again for your help.
> Carlo
> 
> 
> David Sugar ha scritto:
>> What you are thinking of is something like this:
>>
>> 	Semaphore semimutex(1);
>>
>> 	...
>> 	if(isPending(pendingInput)) {
>> 		if(!semimutex.wait(timeout)) {
>> 			library must have crashed, etc...
>> 		}
>> 		call library function ...
>> 		semimutex.post();
>> 	}
>>
>> Hence wait is used like a enterMutex, post like a leaveMutex, and only
>> one instance can pass through because it has a count of 1.  Since wait
>> supports a timeout, you can use that for your failure detect.
>>
>> The Common C++ Semaphore is actually implemented as a combination of
>> mutex and a conditional.
>>
>> Wakan wrote:
>>   
>>> Thanks for your reply.
>>> Can you write an example with the semaphore in this context?
>>> Thanks,
>>> Carlo
>>>
>>> Wakan ha scritto:
>>>     
>>>> Thanks for your reply.
>>>> Can you write an example with the semaphore in this context?
>>>> Thanks,
>>>> Carlo
>>>>
>>>> David Sugar ha scritto:
>>>>       
>>>>> I think what he really wants to do is use the Common C++ Semaphore with
>>>>> a count of 1, since semaphore can block with a "timeout", and with a "1"
>>>>> count in effect acts as a mutex...
>>>>>
>>>>> The larger question though of what to do with the stuck thread, perhaps
>>>>> from a broken library, is important also.  He could cancel the thread in
>>>>> question if it timed out, and put cleanup code in the thread destructor
>>>>> when he invokes delete to join it, but if the library allocated
>>>>> resources he cannot determine for them to get cleanly deallocated.
>>>>>
>>>>> Conrad T. Pino wrote:
>>>>>   
>>>>>         
>>>>>> You're on the right track.  Please pardon my rusty recollection syntax.
>>>>>> Revise:
>>>>>>
>>>>>> 	mutex.enterMutex();
>>>>>>
>>>>>> to a form that accepts a timeout.  This example won't compile:
>>>>>>
>>>>>> 	const int timeout = 500;
>>>>>>
>>>>>> 	while (1) {
>>>>>> 		if ( isPending( pendingInput ) ) {
>>>>>> 			int result = mutex.enterMutex( timeout );
>>>>>>
>>>>>> 			if ( result == success ) {
>>>>>> 				---> protected function call (a function that can't work 
>>>>>> 				in multithread env) <---       
>>>>>> 				mutex.leaveMutex();
>>>>>> 			} else {
>>>>>> 				// do something else with pending input
>>>>>> 			}
>>>>>> 		}
>>>>>> 	}
>>>>>>
>>>>>> While the above will implement your timeout idea it does nothing about
>>>>>> the fundamental problem.  When the library "breaks" can be discoverd
>>>>>> and the blocked mutex/thread combination can be cancelled/restared
>>>>>> HOWEVER PROPRIETARY LIBRARY STATE IS INCONSISTENT & LIKELY DANGEROUS.
>>>>>>
>>>>>> If the library is dynamically loaded under your control then unload it
>>>>>> and reload it to get it back into a consistent state.  If it's auto or
>>>>>> static linked then you may have an unsolveable problem.
>>>>>>
>>>>>> If a reliable system is your goal then one of these MUST be true:
>>>>>>
>>>>>> 		proprietary library NEVER fails
>>>>>> 	OR
>>>>>> 		proprietary library can be forced back to a consistent
>>>>>> 		state because it has a reload or reinitialize method
>>>>>>
>>>>>> Good luck.
>>>>>>
>>>>>>     
>>>>>>           
>>>>>>> -----Original Message-----
>>>>>>> From: bug-commoncpp-bounces+conrad=pino.com@gnu.org
>>>>>>> [mailto:bug-commoncpp-bounces+conrad=pino.com@gnu.org]On Behalf Of Wakan
>>>>>>> Sent: Saturday, January 27, 2007 07:18
>>>>>>> To: bug-commoncpp@gnu.org
>>>>>>> Subject: can't release mutex
>>>>>>>
>>>>>>> Hi,
>>>>>>> I'm using commoncpp library in a project that includes a multithread 
>>>>>>> server that
>>>>>>> can accept many tcp connection and each connection generates a thread.
>>>>>>> In this server I'm using a thirdy party proprietary library (compiled), 
>>>>>>> that (as the producer says)
>>>>>>> can't work in multithread environment.
>>>>>>> As each connection thread needs to call functions of this thirdy party 
>>>>>>> library, I've used a mutex to protect the piece of
>>>>>>> code where this external library function is called.
>>>>>>> In this way I can use this library fine, because all calls are 
>>>>>>> serialized and the protected function is called by one thread each time.
>>>>>>> This is an example:
>>>>>>> ...
>>>>>>>     while(1) {
>>>>>>>         if(isPending(pendingInput)) {
>>>>>>>                 mutex.enterMutex();
>>>>>>>                 ---> protected function call (a function that can't work 
>>>>>>> in multithread env) <---       
>>>>>>>                 mutex.leaveMutex();
>>>>>>>        }
>>>>>>>     }
>>>>>>> ...
>>>>>>> in 99% of cases it works fine. But it accidentally happens that a thread 
>>>>>>> can't exit from the mutex
>>>>>>> maybe because the thirdy party function freezes itself.
>>>>>>> When this happens, the server can accept other connections, soit still 
>>>>>>> works, but each thread can't enter in the mutex proteced piece of code.
>>>>>>> I'm thinking about something, like a timeout, that exits the mutex after 
>>>>>>> a time, if the thread is not exiting...
>>>>>>> Can someone help me to resolve this problem? Are there other solutions?
>>>>>>> Thanks in advance,
>>>>>>> Regards
>>>>>>> Carlo
>>>>>>>       
>>>>>>>             
>>>>>> _______________________________________________
>>>>>> Bug-commoncpp mailing list
>>>>>> Bug-commoncpp@gnu.org
>>>>>> http://lists.gnu.org/mailman/listinfo/bug-commoncpp
>>>>>>     
>>>>>>           
>>>>> __________ NOD32 2011 (20070127) Information __________
>>>>>
>>>>> This message was checked by NOD32 antivirus system.
>>>>> http://www.eset.com
>>>>>
>>>>>   
>>>>>         
>>>>
>>>> __________ NOD32 2014 (20070128) Information __________
>>>>
>>>> This message was checked by NOD32 antivirus system.
>>>> http://www.eset.com
>>>> ------------------------------------------------------------------------
>>>>
>>>> _______________________________________________
>>>> Bug-commoncpp mailing list
>>>> Bug-commoncpp@gnu.org
>>>> http://lists.gnu.org/mailman/listinfo/bug-commoncpp
>>>>
>>>>
>>>> __________ NOD32 2014 (20070128) Information __________
>>>>
>>>> This message was checked by NOD32 antivirus system.
>>>> http://www.eset.com
>>>>
>>>>   
>>>>       
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> Bug-commoncpp mailing list
>>> Bug-commoncpp@gnu.org
>>> http://lists.gnu.org/mailman/listinfo/bug-commoncpp
>>>     
>>
>>
>> __________ NOD32 2014 (20070128) Information __________
>>
>> This message was checked by NOD32 antivirus system.
>> http://www.eset.com
>>
>>   
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Bug-commoncpp mailing list
> Bug-commoncpp@gnu.org
> http://lists.gnu.org/mailman/listinfo/bug-commoncpp

--------------060402090703080509050309
Content-Type: text/x-vcard; charset=utf-8;
 name="dyfet.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="dyfet.vcf"

begin:vcard
fn:David Sugar
n:Sugar;David
org:GNU Telephony
email;internet:dyfet@gnutelephony.org
tel;work:+1 201 215 2609
url:http://www.gnutelephony.org
version:2.1
end:vcard


--------------060402090703080509050309--



From MAILER-DAEMON Wed Jan 31 19:30:46 2007
Received: from mailman by lists.gnu.org with archive (Exim 4.43)
	id 1HCPqf-0002f5-SZ
	for mharc-bug-commoncpp@gnu.org; Wed, 31 Jan 2007 19:30:45 -0500
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1HCNLN-0003pH-Ak
	for bug-commoncpp@gnu.org; Wed, 31 Jan 2007 16:50:17 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1HCNLK-0003p5-Ta
	for bug-commoncpp@gnu.org; Wed, 31 Jan 2007 16:50:16 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1HCNLK-0003p2-PC
	for bug-commoncpp@gnu.org; Wed, 31 Jan 2007 16:50:14 -0500
Received: from 80-47-244-18.lond-th.dynamic.dial.as9105.com ([80.47.244.18]
	helo=dell.purcell.id.au)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32)
	(Exim 4.52) id 1HCNLK-0000Ck-B3
	for bug-commoncpp@gnu.org; Wed, 31 Jan 2007 16:50:14 -0500
Received: from mark by dell.purcell.id.au with local (Exim 4.63)
	(envelope-from <msp@debian.org>)
	id 1HCNLH-0001JZ-2H; Wed, 31 Jan 2007 21:50:11 +0000
From: Mark Purcell <msp@debian.org>
Organization: Debian GNU/Linux
To: bug-commoncpp@gnu.org
Date: Wed, 31 Jan 2007 19:39:42 +0000
User-Agent: KMail/1.9.5
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart2097055.fB9ja79Sb6";
	protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <200701311939.42860.msp@debian.org>
X-detected-kernel: FreeBSD 4.4 (1)
X-Mailman-Approved-At: Wed, 31 Jan 2007 19:30:44 -0500
Cc: 356601-forwarded@bugs.debian.org
Subject: makes other packages FTBFS with G++ 4.1: endKeydata was not declared
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/bug-commoncpp>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Jan 2007 21:50:17 -0000

--nextPart2097055.fB9ja79Sb6
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

David,

Find enclosed a patch you may wish to include upstream.

Thanks,
Mark


  * Thanks to Jonas Meyer & Amaya for picking up a typo in the
    debian/patches/
    - Fixes: makes other packages FTBFS with G++ 4.1: endKeydata was not declared
    in this scope (Closes: #356601)

diff -urNad libcommoncpp2-1.3.26~/include/cc++/misc.h libcommoncpp2-1.3.26/include/cc++/misc.h
--- libcommoncpp2-1.3.26~/include/cc++/misc.h   2006-03-28 16:09:04.000000000 +0100
+++ libcommoncpp2-1.3.26/include/cc++/misc.h    2006-04-12 19:19:25.000000000 +0100
@@ -343,6 +343,9 @@
  * @author David Sugar <dyfet@ostel.com>
  * @short load text configuration files into keyword pairs.
  */
+
+void endKeydata(void);
+
 class __EXPORT Keydata : protected MemPager
 {
 public:

--nextPart2097055.fB9ja79Sb6
Content-Type: application/pgp-signature

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

iD8DBQBFwPB+oCzanz0IthIRAv9zAJ9oYSy80a8E8iFQRRW0aAIoMN+tZQCfdSuz
yZVyj6As2/s6yho3Zn5w/EM=
=wUT8
-----END PGP SIGNATURE-----

--nextPart2097055.fB9ja79Sb6--



From MAILER-DAEMON Wed Jan 31 19:30:46 2007
Received: from mailman by lists.gnu.org with archive (Exim 4.43)
	id 1HCPqg-0002fV-5c
	for mharc-bug-commoncpp@gnu.org; Wed, 31 Jan 2007 19:30:46 -0500
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1HCOBL-00079p-GZ
	for bug-commoncpp@gnu.org; Wed, 31 Jan 2007 17:43:59 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1HCOBJ-00079d-29
	for bug-commoncpp@gnu.org; Wed, 31 Jan 2007 17:43:58 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1HCOBI-00079a-Si
	for bug-commoncpp@gnu.org; Wed, 31 Jan 2007 17:43:56 -0500
Received: from 80-47-244-18.lond-th.dynamic.dial.as9105.com ([80.47.244.18]
	helo=dell.purcell.id.au)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32)
	(Exim 4.52) id 1HCOBI-00004v-C9
	for bug-commoncpp@gnu.org; Wed, 31 Jan 2007 17:43:56 -0500
Received: from mark by dell.purcell.id.au with local (Exim 4.63)
	(envelope-from <msp@debian.org>)
	id 1HCNLG-0001JK-2b; Wed, 31 Jan 2007 21:50:10 +0000
From: Mark Purcell <msp@debian.org>
Organization: Debian GNU/Linux
To: bug-commoncpp@gnu.org
Date: Wed, 31 Jan 2007 19:36:50 +0000
User-Agent: KMail/1.9.5
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart9618172.CFBYuk5ETL";
	protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <200701311936.52114.msp@debian.org>
X-detected-kernel: Windows 2000 SP4, XP SP1+
X-Greylist: delayed 3225 seconds by postgrey-1.27 at monty-python;
	Wed, 31 Jan 2007 17:43:56 EST
X-Mailman-Approved-At: Wed, 31 Jan 2007 19:30:44 -0500
Cc: Yan Morin <yan.morin@savoirfairelinux.com>,
	360492-forwarded@bugs.debian.org
Subject: error: invalid function declaration
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/bug-commoncpp>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Jan 2007 22:43:59 -0000

--nextPart9618172.CFBYuk5ETL
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

David,

Find enclosed a patch to fixup an invalid function declaration, you might wish to include upstream.

Thanks,
Mark

## bug360492.dpatch by  Yan Morin <yan.morin@savoirfairelinux.com>
##
## All lines beginning with `## DP:' are a description of the patch.
## DP: http://bugs.debian.org/360492

@DPATCH@
diff -urNad libcommoncpp2-1.3.26~/template/pointer.h libcommoncpp2-1.3.26/template/pointer.h
--- libcommoncpp2-1.3.26~/template/pointer.h    2006-02-25 23:36:00.000000000 +0000
+++ libcommoncpp2-1.3.26/template/pointer.h     2006-04-18 23:09:29.000000000 +0100
@@ -43,6 +43,10 @@
  * @short Template for creating reference count managed smart pointers.
  **/

+#ifndef CCXX_MISSING_H_
+#include <cc++/missing.h>
+#endif
+
 namespace ost {

 /**

--nextPart9618172.CFBYuk5ETL
Content-Type: application/pgp-signature

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

iD8DBQBFwO/UoCzanz0IthIRAvy8AJ9e/r1wh3QuOprNRJSR3XbfxSRClACfTDu4
HvVJC3vyP0b381f5u7Om72E=
=ERJ8
-----END PGP SIGNATURE-----

--nextPart9618172.CFBYuk5ETL--



From MAILER-DAEMON Wed Jan 31 19:30:46 2007
Received: from mailman by lists.gnu.org with archive (Exim 4.43)
	id 1HCPqg-0002f9-0e
	for mharc-bug-commoncpp@gnu.org; Wed, 31 Jan 2007 19:30:46 -0500
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1HCNYA-0002ZN-GH
	for bug-commoncpp@gnu.org; Wed, 31 Jan 2007 17:03:30 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1HCNY9-0002ZB-52
	for bug-commoncpp@gnu.org; Wed, 31 Jan 2007 17:03:29 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1HCNY8-0002Z8-VX
	for bug-commoncpp@gnu.org; Wed, 31 Jan 2007 17:03:29 -0500
Received: from mx20.gnu.org ([199.232.41.8])
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32)
	(Exim 4.52) id 1HCNY8-00024x-GO
	for bug-commoncpp@gnu.org; Wed, 31 Jan 2007 17:03:28 -0500
Received: from 80-47-244-18.lond-th.dynamic.dial.as9105.com ([80.47.244.18]
	helo=dell.purcell.id.au) by mx20.gnu.org with esmtp (Exim 4.52)
	id 1HCNY7-0004cJ-9x
	for bug-commoncpp@gnu.org; Wed, 31 Jan 2007 17:03:28 -0500
Received: from mark by dell.purcell.id.au with local (Exim 4.63)
	(envelope-from <msp@debian.org>)
	id 1HCNLD-0001J3-QQ; Wed, 31 Jan 2007 21:50:08 +0000
From: Mark Purcell <msp@debian.org>
Organization: Debian GNU/Linux
To: bug-commoncpp@gnu.org
Date: Wed, 31 Jan 2007 19:31:12 +0000
User-Agent: KMail/1.9.5
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart1767253.DZeRDLFK6d";
	protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <200701311931.21207.msp@debian.org>
X-detected-kernel: Solaris 9
X-detected-kernel: Linux 2.6, seldom 2.4 (older, 4)
X-Mailman-Approved-At: Wed, 31 Jan 2007 19:30:44 -0500
Cc: 403719-forwarded@bugs.debian.org, Petr Salinger <Petr.Salinger@seznam.cz>
Subject: Fwd: Bug#403719: libcommoncpp2: FTBFS on GNU/kFreeBSD
X-BeenThere: bug-commoncpp@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports for Common C++ <bug-commoncpp.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/bug-commoncpp>
List-Post: <mailto:bug-commoncpp@gnu.org>
List-Help: <mailto:bug-commoncpp-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/bug-commoncpp>,
	<mailto:bug-commoncpp-request@gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Jan 2007 22:03:30 -0000

--nextPart1767253.DZeRDLFK6d
Content-Type: multipart/mixed;
  boundary="Boundary-01=_C6OwFlcxVVYxNrR"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--Boundary-01=_C6OwFlcxVVYxNrR
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

David,

Find enclosed a patch to enable libcommoncpp2 to build on GNU/kFreeBSD you might wish to include upstream.

Thanks,
Mark

----------  Forwarded Message  ----------

Subject: Bug#403719: libcommoncpp2: FTBFS on GNU/kFreeBSD
Date: Tuesday 19 December 2006 10:37
From: Petr Salinger <Petr.Salinger@seznam.cz>
To: submit@bugs.debian.org

Package: libcommoncpp2
Severity: important
Version: 1.5.3-2
Tags: patch

Hi,

the current version fails to build on GNU/kFreeBSD.

It needs small fix-up, see attached patch.

It would also be nice if you can ask upstream
to include this change.

Thanks in advance

                         Petr


-------------------------------------------------------

--Boundary-01=_C6OwFlcxVVYxNrR
Content-Type: TEXT/plain;
  charset="us-ascii";
  name="libcommoncpp2.diff"
Content-Transfer-Encoding: BASE64
Content-Disposition: attachment; filename=libcommoncpp2.diff

b25seSBpbiBwYXRjaDI6DQp1bmNoYW5nZWQ6DQotLS0gbGliY29tbW9uY3Bw
Mi0xLjUuMy5vcmlnL3NyYy9zb2NrZXQuY3BwDQorKysgbGliY29tbW9uY3Bw
Mi0xLjUuMy9zcmMvc29ja2V0LmNwcA0KQEAgLTE2MTYsNyArMTYxNiw3IEBA
DQogCWludCByZXR2YWwgPSBzZXRzb2Nrb3B0KHNvLCBJUFBST1RPX0lQLCBJ
UF9BRERfTUVNQkVSU0hJUCwgKGNoYXIgKikmZ3JvdXAsIHNpemVvZihncm91
cCkpOw0KIAlyZXR1cm4gZXJyU3VjY2VzczsNCiANCi0jZWxpZiBkZWZpbmVk
KElQX0FERF9NRU1CRVJTSElQKSAmJiBkZWZpbmVkKFNJT0NHSUZJTkRFWCkg
JiYgIWRlZmluZWQoX19GcmVlQlNEX18pICYmICFkZWZpbmVkKF9PU0ZfU09V
UkNFKSAmJiAhZGVmaW5lZChfX2hwdXgpICYmICFkZWZpbmVkKF9fR05VX18p
DQorI2VsaWYgZGVmaW5lZChJUF9BRERfTUVNQkVSU0hJUCkgJiYgZGVmaW5l
ZChTSU9DR0lGSU5ERVgpICYmICFkZWZpbmVkKF9fRnJlZUJTRF9fKSAmJiAh
ZGVmaW5lZChfX0ZyZWVCU0Rfa2VybmVsX18pICYmICFkZWZpbmVkKF9PU0Zf
U09VUkNFKSAmJiAhZGVmaW5lZChfX2hwdXgpICYmICFkZWZpbmVkKF9fR05V
X18pDQogICAgICAgICANCiAJCXN0cnVjdCBpcF9tcmVxbiAgICAgIGdyb3Vw
Ow0KICAgICAgICAgc3RydWN0IHNvY2thZGRyX2luICAgbXlhZGRyOw0KQEAg
LTE2NTYsNyArMTY1Niw3IEBADQogU29ja2V0OjpFcnJvciBVRFBTb2NrZXQ6
OmdldEludGVyZmFjZUluZGV4KGNvbnN0IGNoYXIgKkRldmljZU5hbWUsaW50
JiBJbnRlcmZhY2VJbmRleCkNCiB7DQogI2lmbmRlZiBXSU4zMg0KLSNpZiBk
ZWZpbmVkKElQX0FERF9NRU1CRVJTSElQKSAmJiBkZWZpbmVkKFNJT0NHSUZJ
TkRFWCkgJiYgIWRlZmluZWQoX19GcmVlQlNEX18pICYmICFkZWZpbmVkKF9P
U0ZfU09VUkNFKSAmJiAhZGVmaW5lZChfX2hwdXgpICYmICFkZWZpbmVkKF9f
R05VX18pDQorI2lmIGRlZmluZWQoSVBfQUREX01FTUJFUlNISVApICYmIGRl
ZmluZWQoU0lPQ0dJRklOREVYKSAmJiAhZGVmaW5lZChfX0ZyZWVCU0RfXykg
JiYgIWRlZmluZWQoX19GcmVlQlNEX2tlcm5lbF9fKSAmJiAhZGVmaW5lZChf
T1NGX1NPVVJDRSkgJiYgIWRlZmluZWQoX19ocHV4KSAmJiAhZGVmaW5lZChf
X0dOVV9fKQ0KIA0KICAgc3RydWN0IGlwX21yZXFuICBtcmVxbjsNCiAgIHN0
cnVjdCBpZnJlcSAgICAgbV9pZnJlcTsNCg==

--Boundary-01=_C6OwFlcxVVYxNrR--

--nextPart1767253.DZeRDLFK6d
Content-Type: application/pgp-signature

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

iD8DBQBFwO6JoCzanz0IthIRAhD0AJ9uJPh7UoWKVftQIFGdqLj8nHBg4ACgk6j4
BTY4/A/tD31SNd0jNlxqZFk=
=ijwx
-----END PGP SIGNATURE-----

--nextPart1767253.DZeRDLFK6d--



