(at the time of writing this bug report, the archive didn't index those mails yet so I can't give an url)
Wrong, I was just too stupid to realize that the thread view of the archives have a "next" page link (and that the date of last update is only referring to the current page).
See: http://lists.debian.org/debian-user/2008/08/thrd4.html#01793
top of a "bt full", which indicates that glibc complains about a double free
Well, or maybe rather a memory corruption, since glibc seemingly *tried* to emit a "double free or corruption (!prev)" message, which probably would have succeeded if there wasn't a segfault while trying to do that (meaning that something more severe is going wrong; I think glibc tries to get a backtrace and memory map in such a case, which may be the point where it fails; otoh, gdb didn't have problems showing the backtrace).
Christian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
