Your message dated Thu, 04 Oct 2007 12:32:02 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#432729: fixed in log4cpp 1.0-1
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: liblog4cpp4
Version: 0.3.5-rc3-1
It seems that there are still thread safety issues. The Shibboleth
project uses this library, but the developers have applied patches to
fix those problems. The Shibboleth Service Provider software has become
part of the Etch distribution and thus dependant on the log4cpp library.
However, the Shibboleth daemon often crashes, expecially when under
heavy traffic and it seems that the problem is in the log4cpp library,
see the gdb output:
(gdb) bt
#0 0xb7f46410 in ?? ()
#1 0xafff36ec in ?? ()
#2 0x00000006 in ?? ()
#3 0x00004b91 in ?? ()
#4 0xb753e811 in raise () from /lib/tls/i686/cmov/libc.so.6
#5 0xb753ffb9 in abort () from /lib/tls/i686/cmov/libc.so.6
#6 0xb7573d3a in __fsetlocking () from /lib/tls/i686/cmov/libc.so.6
#7 0xb757b5cf in mallopt () from /lib/tls/i686/cmov/libc.so.6
#8 0xb757b672 in free () from /lib/tls/i686/cmov/libc.so.6
#9 0xb77383b1 in operator delete () from /usr/lib/libstdc++.so.6
#10 0xb7e80cae in std::vector<log4cpp::NDC::DiagnosticContext,
std::allocator<log4cpp::NDC::DiagnosticContext> >::_M_insert_aux ()
from /usr/lib/liblog4cpp.so.4
#11 0xb7e80639 in log4cpp::NDC::_push () from /usr/lib/liblog4cpp.so.4
#12 0xb7e7f906 in log4cpp::NDC::push () from /usr/lib/liblog4cpp.so.4
#13 0xb7dd927d in saml::NDC::NDC () from /usr/lib/libsaml.so.5
#14 0x08050eb0 in xercesc_2_7::XMLDeleter::~XMLDeleter ()
#15 0x08052961 in shibboleth::InvalidSessionException::~InvalidSessionException
()
#16 0xb7607380 in svc_getreq_common () from /lib/tls/i686/cmov/libc.so.6
#17 0xb7606cdf in svc_getreqset () from /lib/tls/i686/cmov/libc.so.6
#18 0x0804e105 in xercesc_2_7::XMLDeleter::~XMLDeleter ()
#19 0x0804e3e1 in xercesc_2_7::XMLDeleter::~XMLDeleter ()
#20 0xb764c240 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#21 0xb75e13de in clone () from /lib/tls/i686/cmov/libc.so.6
--------------------------------
Core was generated by `/usr/sbin/shibd -p /var/run/shibd.pid'.
Program terminated with signal 6, Aborted.
#0 0xb7fdd410 in ?? ()
(gdb) bt
#0 0xb7fdd410 in ?? ()
#1 0xb046973c in ?? ()
#2 0x00000006 in ?? ()
#3 0x00004db8 in ?? ()
#4 0xb75d5811 in raise () from /lib/tls/i686/cmov/libc.so.6
#5 0xb75d6fb9 in abort () from /lib/tls/i686/cmov/libc.so.6
#6 0xb760ad3a in __fsetlocking () from /lib/tls/i686/cmov/libc.so.6
#7 0xb76125cf in mallopt () from /lib/tls/i686/cmov/libc.so.6
#8 0xb7612672 in free () from /lib/tls/i686/cmov/libc.so.6
#9 0xb77cf3b1 in operator delete () from /usr/lib/libstdc++.so.6
#10 0xb77abebd in std::string::_Rep::_M_destroy () from /usr/lib/libstdc++.so.6
#11 0xb7f1743d in log4cpp::NDC::_pop () from /usr/lib/liblog4cpp.so.4
#12 0xb7f1693b in log4cpp::NDC::pop () from /usr/lib/liblog4cpp.so.4
#13 0xb7e70a42 in saml::NDC::~NDC () from /usr/lib/libsaml.so.5
#14 0x0805133c in xercesc_2_7::XMLDeleter::~XMLDeleter ()
#15 0x08052961 in shibboleth::InvalidSessionException::~InvalidSessionException
()
#16 0xb769e380 in svc_getreq_common () from /lib/tls/i686/cmov/libc.so.6
#17 0xb769dcdf in svc_getreqset () from /lib/tls/i686/cmov/libc.so.6
#18 0x0804e105 in xercesc_2_7::XMLDeleter::~XMLDeleter ()
#19 0x0804e3e1 in xercesc_2_7::XMLDeleter::~XMLDeleter ()
#20 0xb76e3240 in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#21 0xb76783de in clone () from /lib/tls/i686/cmov/libc.so.6
Shibboleth home page: http://shibboleth.internet2.edu/
Note about the log4cpp issues:
https://spaces.internet2.edu/display/SHIB/Log4Cpp
Those crashes occur on different hardware architectures, on Debian Etch.
When using the version modified by Internet2, no crashes occur.
Modified (working) version is available here:
http://shibboleth.internet2.edu/downloads/
--
-----------------------------------------------------------
Ing. Ivan Novakov <[EMAIL PROTECTED]>
Faculty of Electrical Engineering CTU in Prague
http://www.fel.cvut.cz/
-----------------------------------------------------------
smime.p7s
Description: S/MIME Cryptographic Signature
--- End Message ---
--- Begin Message ---
Source: log4cpp
Source-Version: 1.0-1
We believe that the bug you reported is fixed in the latest version of
log4cpp, which is due to be installed in the Debian FTP archive:
liblog4cpp4-dev_1.0-1_amd64.deb
to pool/main/l/log4cpp/liblog4cpp4-dev_1.0-1_amd64.deb
liblog4cpp4_1.0-1_amd64.deb
to pool/main/l/log4cpp/liblog4cpp4_1.0-1_amd64.deb
log4cpp_1.0-1.diff.gz
to pool/main/l/log4cpp/log4cpp_1.0-1.diff.gz
log4cpp_1.0-1.dsc
to pool/main/l/log4cpp/log4cpp_1.0-1.dsc
log4cpp_1.0.orig.tar.gz
to pool/main/l/log4cpp/log4cpp_1.0.orig.tar.gz
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Fathi Boudra <[EMAIL PROTECTED]> (supplier of updated log4cpp package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Thu, 04 Oct 2007 09:11:00 +0200
Source: log4cpp
Binary: liblog4cpp4 liblog4cpp4-dev
Architecture: source amd64
Version: 1.0-1
Distribution: unstable
Urgency: low
Maintainer: Fathi Boudra <[EMAIL PROTECTED]>
Changed-By: Fathi Boudra <[EMAIL PROTECTED]>
Description:
liblog4cpp4 - C++ library for flexible logging (runtime)
liblog4cpp4-dev - C++ library for flexible logging (development)
Closes: 432729 445173
Changes:
log4cpp (1.0-1) unstable; urgency=low
.
* New upstream release. (Closes: #432729, #445173)
* Switch to cdbs/quilt.
* Remove patches. Merged upstream.
* Update control:
* Remove dpatch, libtool, automake1.9 build-dependencies.
* Add cdbs and quilt build-dependencies.
* Bump Standards-Version to 3.7.2.
* Add missing files in liblog4cpp4-dev.install:
* log4cpp-config
* log4cpp.m4
* Add -lpthread to LDFLAGS to fix FTBFS.
Files:
5c11606555880d8ba00cd161b1c5b77a 582 libs optional log4cpp_1.0-1.dsc
1face50ead0790d1297dfb04bacf273c 495726 libs optional log4cpp_1.0.orig.tar.gz
2fe44428beca701a8ead762ae02cfb30 5058 libs optional log4cpp_1.0-1.diff.gz
ae86d66b64bf51fe4c5d172019d2295d 214370 libdevel optional
liblog4cpp4-dev_1.0-1_amd64.deb
8170365bafddae8e49577affd0fbf01f 128554 libs optional
liblog4cpp4_1.0-1_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHBNXJvGr7W6HudhwRArtLAJsGhFnhbfWTW4y9Am4oessCVfKtSACeJtD3
9wCGrbAUyQv6wNAaNNLAve0=
=Y7pq
-----END PGP SIGNATURE-----
--- End Message ---
