i'm getting the following crash after the recent updates of glibc when using mozilla-firefox-bin-3.0_beta2: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xeefffb90 (LWP 30931)] 0x0804ea87 in free () (gdb) bt #0 0x0804ea87 in free () #1 0xf677c69f in __res_iclose () from /lib32/libc.so.6 #2 0xf67ade57 in ?? () from /lib32/libc.so.6 #3 0xeefffdf4 in ?? () #4 0x00000001 in ?? () #5 0xf67dcff4 in ?? () from /lib32/libc.so.6 #6 0xf67db270 in ?? () from /lib32/libc.so.6 #7 0xeefff3c8 in ?? () #8 0xf67addda in __libc_thread_freeres () from /lib32/libc.so.6 Backtrace stopped: frame did not save the PC i hope having glibc with debug-flag is enough for this trace. it doesn't matter what i do, even when i do not touch the browser at all this happens. those crashes started after my recent update, so the latest glibc-version seems to be the problem - i used the browser for days now (since it hit portage) without a problem. i also have this type of crashes on a x86-machine (but did not trace them, though) - when i get to the machine i'll backtrace it, i think it's the same. so seems no amd64-specific problem. if you need more debug-output, tell me what to do and i'll post it. Reproducible: Always Steps to Reproduce: 1. update to latest versions 2. open browser and wait 3. Actual Results: segfault
i forgot some things (since i had to write this bug fast before the next crash ;) ): the trace is from an amd64-system and crashes happen randomly about 5-20mins after starting the browser.
Created attachment 176889 [details] emerge --info
the same (similar backtrace) happend just to mozilla-thunderbird-bin-3.0_beta1
*** This bug has been marked as a duplicate of bug 252302 ***
