GNOME Bugzilla – Bug 365600
crash in Epiphany Web Bookmarks:
Last modified: 2006-12-24 13:14:38 UTC
Version: 2.16.1 What were you doing when the application crashed? Distribution: Unknown Gnome Release: 2.16.1 2006-10-15 (FreeBSD GNOME Project) BugBuddy Version: 2.16.0 Memory status: size: 54018048 vsize: 0 resident: 54018048 share: 0 rss: 88182784 rss_rlim: 0 CPU usage: start_time: -2065503700 rtime: 270521 utime: 476802361 stime: 0 cutime:476802361 cstime: 0 timeout: 29850481 it_real_value: 0 frequency: 48422 Backtrace was generated from '/usr/local/bin/epiphany' (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)...(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)...[New Thread 0x888b400 (runnable)] [New Thread 0x8be1200 (runnable)] [New Thread 0x8872c00 (sleeping)] [New Thread 0x83e5200 (runnable)] [New Thread 0x83e5000 (LWP 100214)] [New Thread 0x814c000 (runnable)] [New LWP 100157] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Switching to LWP 100157] 0x291144f7 in pthread_testcancel () from /lib/libpthread.so.2
+ Trace 78695
Thread 7 (LWP 100157)
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
I didn't mean to report this. I hit the wrong button when bug-buddy popped up on close. If I report a crash, I always include full symbols or a patch. If this happens again, I will do a proper report. You can close this.
*** Bug 365831 has been marked as a duplicate of this bug. ***
I'll leave it open because of the duplicate. Apparently more people experience the problem.
*** Bug 367866 has been marked as a duplicate of this bug. ***
*** Bug 366769 has been marked as a duplicate of this bug. ***
*** Bug 366857 has been marked as a duplicate of this bug. ***
*** Bug 368279 has been marked as a duplicate of this bug. ***
*** Bug 377518 has been marked as a duplicate of this bug. ***
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!