GNOME Bugzilla – Bug 144944
Systematic galeon crash on www.frenchmozilla.org
Last modified: 2004-12-22 21:47:04 UTC
Open www.frenchmozilla.org in galeon (this is kind'of embarrassing isn't it?)
same result on java.debian.net
Both work fine here with cvs and mozilla 1.6 Please provide a trace of the crash. (http://bugzilla.gnome.org/getting-traces.cgi)
Fresh stack generated by opening http://bugzilla.gnome.org/getting-traces.cgi ;) Backtrace was generated from '/usr/bin/galeon-bin' Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 1074699872 (LWP 22506)] [New Thread 1162648496 (LWP 22518)] [Thread debugging using libthread_db enabled] [New Thread 1074699872 (LWP 22506)] [New Thread 1162648496 (LWP 22518)] [Thread debugging using libthread_db enabled] [New Thread 1074699872 (LWP 22506)] [New Thread 1162648496 (LWP 22518)] [New Thread 1154255792 (LWP 22517)] [New Thread 1131322288 (LWP 22516)] [New Thread 1122929584 (LWP 22515)] [New Thread 1114344368 (LWP 22514)] [New Thread 1105734576 (LWP 22512)] [New Thread 1093192624 (LWP 22511)] 0xffffe410 in ?? ()
+ Trace 47252
Thread 8 (Thread 1093192624 (LWP 22511))
Another on java.debian.net Backtrace was generated from '/usr/bin/galeon-bin' Using host libthread_db library "/lib/tls/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 1074699872 (LWP 22711)] [New Thread 1154255792 (LWP 22729)] [Thread debugging using libthread_db enabled] [New Thread 1074699872 (LWP 22711)] [New Thread 1154255792 (LWP 22729)] [Thread debugging using libthread_db enabled] [New Thread 1074699872 (LWP 22711)] [New Thread 1154255792 (LWP 22729)] [New Thread 1132014512 (LWP 22728)] [New Thread 1123621808 (LWP 22727)] [New Thread 1114352560 (LWP 22719)] [New Thread 1105783728 (LWP 22717)] [New Thread 1093192624 (LWP 22716)] 0xffffe410 in ?? ()
+ Trace 47253
Thread 7 (Thread 1093192624 (LWP 22716))
/usr/share/bug-buddy/gdb-cmd:2: Error in sourced command file: Unhandled dwarf expression opcode 0x93
*** This bug has been marked as a duplicate of 144012 ***