GNOME Bugzilla – Bug 438221
crash in html_object_get_left_margin
Last modified: 2007-08-01 04:30:24 UTC
What were you doing when the application crashed? selecting an email - which I wanted to read Distribution: Debian 3.1 (sarge) Gnome Release: 2.18.1 2007-04-25 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.21.1-sonne #4 SMP PREEMPT Sat May 12 18:30:35 CEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 166223872 vsize: 166223872 resident: 66154496 share: 20049920 rss: 66154496 rss_rlim: 4294967295 CPU usage: start_time: 1179102648 rtime: 4211 utime: 2944 stime: 1267 cutime:4 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution-2.10' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1233578304 (LWP 26132)] [New Thread -1321882736 (LWP 26221)] [New Thread -1297998960 (LWP 26219)] [New Thread -1323304048 (LWP 26190)] [New Thread -1289581680 (LWP 26147)] [New Thread -1278223472 (LWP 26144)] [New Thread -1269830768 (LWP 26143)] [New Thread -1261438064 (LWP 26142)] [New Thread -1251488880 (LWP 26141)] [New Thread -1242969200 (LWP 26140)] 0xb7f63410 in __kernel_vsyscall ()
+ Trace 134024
Thread 1 (Thread -1233578304 (LWP 26132))
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!
*** Bug 440633 has been marked as a duplicate of this bug. ***
*** Bug 444156 has been marked as a duplicate of this bug. ***
*** Bug 448685 has been marked as a duplicate of this bug. ***
*** Bug 448878 has been marked as a duplicate of this bug. ***
I'm having a hard time trying to find how to produce a usefull trace. I read the informations at http://live.gnome.org/GettingTraces/DistroSpecificInstructions#head-03141be8abf242e942022c6d56fe152e2c9791ef and http://wiki.debian.org/HowToGetABacktrace and all the relevant -dbg packages were already installed on my system before the crash occured, but it seems they were not taken into account (especially the libglib*-dbg and libgtkhtml*-dbg). Do you have some more specific pointers about how to solve that ? Thanks in advance
gerald: that seems to be a general issue on some distros (not only debian). the debian folks (at least loïc) are aware of this problem (bug 460513 comment 4). not much we can do... :-( this is a duplicate of bug 426496. *** This bug has been marked as a duplicate of 426496 ***