On Fri, Jan 13, 2006 at 11:15:14PM +0100, Yann Dirson <[EMAIL PROTECTED]> was 
heard to say:
> I got a segfault with a very similar backtrace, but I had just
> requested an update, from an aptitude running for several hours (it
> had run an upgrade yesterday night).
> 
> (gdb) bt
> #0  0x4011ed45 in __pthread_alt_unlock () from /lib/libpthread.so.0
> #1  0x4011bae4 in pthread_mutex_unlock () from /lib/libpthread.so.0
> #2  0x0814683f in pkgSimulate::Policy::~Policy ()
> #3  0x080eb28e in std::basic_string<char, std::char_traits<char>, 
> std::allocator<char> >::basic_string<__gnu_cxx::__normal_iterator<char 
> const*, std::string> > ()
> #4  0x08053289 in ?? ()
> #5  0x4028a413 in __libc_start_main () from /lib/libc.so.6
> #6  0x08051a11 in ?? ()
> (gdb) 
> 
> Core file still available (for my own reference: core.10282).

  This is a different crash: the other one was caused by a specific bug in
the 'source' command-line function and has been fixed in the current
development version.

  Daniel

Attachment: signature.asc
Description: Digital signature

Reply via email to