GNOME Bugzilla – Bug 362609
crash in Epiphany Web Bookmarks: trying to print a local ...
Last modified: 2006-12-18 13:20:22 UTC
Version: 2.16.1 What were you doing when the application crashed? trying to print a local htm file from epiphany Distribution: Unknown Gnome Release: 2.16.1 2006-10-02 (Archlinux) BugBuddy Version: 2.16.0 Memory status: size: 107696128 vsize: 0 resident: 107696128 share: 0 rss: 32964608 rss_rlim: 0 CPU usage: start_time: 1161005963 rtime: 0 utime: 264 stime: 0 cutime:242 cstime: 0 timeout: 22 it_real_value: 0 frequency: 0 Backtrace was generated from '/opt/gnome/bin/epiphany' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1239627040 (LWP 19476)] [New Thread -1297695840 (LWP 19508)] [New Thread -1289303136 (LWP 19507)] [New Thread -1263027296 (LWP 19480)] [New Thread -1254634592 (LWP 19479)] [New Thread -1246241888 (LWP 19478)] (no debugging symbols found) 0xb7f50410 in ?? ()
+ Trace 76610
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.
to be honest, I don"t feel to much about recompiling gnome with debugging support. Or will it help if I only recompile epiphany with debugging support?
we can't say, but of course we'd be happy if you tried... :-)
For usable stack traces you'll need to have at least the mozilla backend, glib, gtk and libgnomeui, and epiphany built with debug symbols.
*** Bug 370399 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!
I had some time now and found an easy way to recompile the packages with debugging symbols on my distribution, but it doesn't seem to be needed, printing local htm files now works without any problems. It seems it is already fixed in epiphany 2.16.2
Great! Thanks for your quick response.