GNOME Bugzilla – Bug 157945
gterminal crashed
Last modified: 2007-04-26 17:26:22 UTC
Distribution: Debian testing/unstable Package: gnome-terminal Severity: normal Version: GNOME2.8.1 2.7.3 Gnome-Distributor: Ubuntu Synopsis: gterminal crashed Bugzilla-Product: gnome-terminal Bugzilla-Component: general Bugzilla-Version: 2.7.3 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gnome-terminal' (no debugging symbols found)...Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 5109)] [New Thread 32769 (LWP 5115)] [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 5109)] [New Thread 32769 (LWP 5115)] [Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 5109)] [New Thread 32769 (LWP 5115)] [New Thread 16386 (LWP 5116)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x0ebcf0a0 in waitpid () from /lib/libpthread.so.0
+ Trace 51842
Thread 1 (Thread 16384 (LWP 5109))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-11-11 08:18 ------- Unknown version 2.7.3 in product gnome-terminal. Setting version to "1.9.x". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-terminal". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was belum2aj@prf.cuni.cz. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Appears to be a unique stack trace, according to the simple-dup-finder.
This happened inside of libc, which should never ever ever crash. I did find a few crashes with re_exec in their stack (the dup finder is -back-!) and they all happened in debian (bug 63169, bug 76078, bug 127290, bug 131868, bug 147300, bug 154442, bug 155700) Reporter, can you reproduce this?
*** Bug 160963 has been marked as a duplicate of this bug. ***
*** Bug 165142 has been marked as a duplicate of this bug. ***
From email: Sorry to approach you like this, but i couldnt submit this on bugzilla. Wouldnt accept my login nor password. I managed to do this crash again mentioned in the bug http://bugzilla.gnome.org/show_bug.cgi?id=157945. I started gnome-terminal. I had screen running on background, so i did screen -r to get it open. After i had gotten it open and moved mouse away on the gnome-terminal, it crashed. I have done this now like 10 times and always it crashes.
*** Bug 301161 has been marked as a duplicate of this bug. ***
*** Bug 300426 has been marked as a duplicate of this bug. ***
*** Bug 302092 has been marked as a duplicate of this bug. ***
Bug 300426 has a stack trace with debugging symbols, which Kjartan neglected to mention. ;-)
This one looks really like a crash inside de regexp() calls in glibc. I see the reporter was using Debian.. I guess installing libc6-dbg and then adding /usr/lib/debug to the LD_LIBRARY_PATH environment variable, could tell us for sure.
*** Bug 326319 has been marked as a duplicate of this bug. ***
This is indeed a glibc issue, present in the old glibc 2.3.2 which ships with Debian sta(b)le. Resolving as NOTGNOME. For more information, see http://bugs.debian.org/237681
*** Bug 337079 has been marked as a duplicate of this bug. ***
*** Bug 338917 has been marked as a duplicate of this bug. ***
*** Bug 346480 has been marked as a duplicate of this bug. ***
*** Bug 357574 has been marked as a duplicate of this bug. ***
*** Bug 425768 has been marked as a duplicate of this bug. ***