Your message dated Sun, 3 Dec 2006 11:52:16 +0000
with message-id <[EMAIL PROTECTED]>
and subject line libcommoncpp2: Conditional.wait(timeout) don't respect timeout
value
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: libcommoncpp2
Severity: normal
Conditional variables are broken, take a look to this source code:
waitInput.enterMutex();
waitInput.wait(20000);
waitInput.leaveMutex();
bug #1: You have to call enterMutex() and leaveMutex() to let
Conditional variable works
bug #2: Timeout value is ignored
Look also this mailinglist post:
http://mail.gnu.org/archive/html/bug-commoncpp/2003-12/msg00067.html
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (650, 'testing'), (600, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.3
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED]
--
| /
| \Byte - Andrea Briganti - [EMAIL PROTECTED]
http://kbytesys.altervista.org - ICQ: 40872731
CSLug member: http://cslug.linux.it - JID: [EMAIL PROTECTED]
*** Un anello per domarli, un anello per ghermirli e nel buio incatenarli
--- End Message ---
--- Begin Message ---
Version: 1.1
I believe this was fixed in version 1.1 of libcommoncpp2
Mark
Re: Interrupt
From: David Sugar
Subject: Re: Interrupt
Date: Mon, 22 Dec 2003 19:11:28 -0500
User-agent: KMail/1.5.3
To get timing to be correct, you need to use the latest savannah cvs (1.1
tree), but also the Conditional object includes it's own mutex object.
Hence, you would use conditional->enterMutex() rather than a foreign mutex.
--- End Message ---
