GNOME Bugzilla – Bug 316859
bug-buddy crash
Last modified: 2006-04-11 19:09:05 UTC
Distribution: Unknown Package: bug-buddy Severity: normal Version: GNOME2.12.0 2.12.0 Gnome-Distributor: SUSE Synopsis: bug-buddy crash Bugzilla-Product: bug-buddy Bugzilla-Component: general Bugzilla-Version: 2.12.0 BugBuddy-GnomeVersion: 2.0 (2.12.0) Description: Description of the crash: Crash while collecting debugging information. Steps to reproduce the crash: 1. Evolution crashed 2. I pressed the key for Debuggung details. 3. After two minutes, backtrace was not yet ready (AMD64, 1GB RAM). I used force-quit applet to kill Evolution. Expected Results: Backtrace in time How often does this happen? Crash for the first time. Collect backtrace never completes - nearly every time. Additional Information: Debugging Information: Backtrace was generated from '/opt/gnome/bin/bug-buddy' (no debugging symbols found) Using host libthread_db library "/lib64/tls/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) [Thread debugging using libthread_db enabled] [New Thread 46912578493760 (LWP 25530)] [New Thread 1074006368 (LWP 25534)] [Thread debugging using libthread_db enabled] [New Thread 46912578493760 (LWP 25530)] [New Thread 1074006368 (LWP 25534)] (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 46912578493760 (LWP 25530)] [New Thread 1074006368 (LWP 25534)] (no debugging symbols found) (no debugging symbols found) 0x00002aaaae1f9f02 in waitpid () from /lib64/tls/libpthread.so.0
+ Trace 63121
Thread 1 (Thread 46912578493760 (LWP 25530))
------- Bug moved to this database by unknown@gnome.bugs 2005-09-21 17:07 UTC ------- Unknown version 2.12.0 in product bug-buddy. Setting version to "2.12.x".
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
This is another crash yet unsent. It is probably net exactly the same crash as the previous, but still in the same circumstances. Bug-buddy on AMD64 is unable to complete backtrace for about 90% of crashes. Pressing Cancel sometimes crashes bug-buddy. Steps to reproduce the crash: 1. Crash of any application 2. Inform developers 3. Show debugging details 4. Wait a minute or hour or so 5. Press Cancel Expected Results: Completed backtrace How often does this happen? Not completing backtrace in about 90%, crash in about 5%. Additional Information: Work-around: Open GEdit, press button to get backtrace on screen, mouse click click into the text area, press Ctrl+A Ctrl+C, go to GEdit, press Ctrl+V. If you are happy, you have a 10000 lines long backtrace containing a lot of lines with zeros. Backtrace examples collected by this way: https://bugzilla.novell.com/show_bug.cgi?id=117813, bug https://bugzilla.novell.com/show_bug.cgi?id=100135#c8, bug 319838 Thousands of lines containing following text were removes:
+ Trace 64167
Thread 1 (Thread 46912578493760 (LWP 32028))
0x00002aaaae1f9ea5 32 return INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);
Have the same problem, see bug 321296 Now I have started gdb manually and it seems like gdb produces and endless backtrace, i.e. the bug would be gdb's fault and not bug-buddy's!
*** This bug has been marked as a duplicate of 321296 ***