Dear Wolfgang, thanks for your answer and sorry for the delay. On Thursday 09 December 2010, 11:41:46 Wolfgang Rosenauer wrote:
Am 09.12.2010 11:17, schrieb Hans-Peter Jansen:
Thread 1 (Thread 0xb7c236d0 (LWP 11475)): #0 0xb7880a0c in ?? () from /usr/lib/xulrunner-1.9.2.12/libmozjs.so #1 0xb7881e37 in js_LookupProperty () from /usr/lib/xulrunner-1.9.2.12/libmozjs.so #2 0xb7881ea6 in ?? () from /usr/lib/xulrunner-1.9.2.12/libmozjs.so #3 0xb7881c9d in ?? () from /usr/lib/xulrunner-1.9.2.12/libmozjs.so #4 0xb785f384 in ?? () from /usr/lib/xulrunner-1.9.2.12/libmozjs.so #5 0xb7870f4b in js_Invoke () from /usr/lib/xulrunner-1.9.2.12/libmozjs.so #6 0xb66295d3 in ?? () from /usr/lib/xulrunner-1.9.2.12/libxul.so #7 0xb6624f83 in ?? () from /usr/lib/xulrunner-1.9.2.12/libxul.so ---Type <return> to continue, or q <return> to quit--- #8 0xb6f4e198 in ?? () from /usr/lib/xulrunner-1.9.2.12/libxul.so #9 0xb66edc65 in ?? () from /usr/lib/xulrunner-1.9.2.12/libxul.so #10 0xb6f40772 in ?? () from /usr/lib/xulrunner-1.9.2.12/libxul.so #11 0xb6f0f00c in ?? () from /usr/lib/xulrunner-1.9.2.12/libxul.so #12 0xb6e840f6 in ?? () from /usr/lib/xulrunner-1.9.2.12/libxul.so #13 0xb6edc99c in MessageLoop::RunInternal() () from /usr/lib/xulrunner-1.9.2.12/libxul.so #14 0xb6edc9c0 in MessageLoop::RunHandler() () from /usr/lib/xulrunner-1.9.2.12/libxul.so #15 0xb6edca37 in ?? () from /usr/lib/xulrunner-1.9.2.12/libxul.so #16 0xb6dfc3bc in ?? () from /usr/lib/xulrunner-1.9.2.12/libxul.so #17 0xb6cc0d30 in ?? () from /usr/lib/xulrunner-1.9.2.12/libxul.so #18 0xb65f2e73 in XRE_main () from /usr/lib/xulrunner-1.9.2.12/libxul.so #19 0x08049f6b in ?? () #20 0xb7c45705 in __libc_start_main (main=0x80499a4 <strcmp@plt+248>, argc=1, ubp_av=0xbfffebd4, init=0x8058400, fini=0x80583f0, rtld_fini=0xb7fef210 <_dl_fini>, stack_end=0xbfffebcc) at libc-start.c:220 #21 0x080498e1 in ?? ()
Here's, what I've installed right now: mozilla-xulrunner192-1.9.2.12-1.2 mozilla-xulrunner192-buildsymbols-1.9.2.12-1.2 mozilla-xulrunner192-debuginfo-1.9.2.12-1.2 mozilla-xulrunner192-debugsource-1.9.2.12-1.2 mozilla-xulrunner192-gnome-1.9.2.12-1.2 mozilla-xulrunner192-translations-common-1.9.2.12-1.2
You need mozilla-js192 and its debuginfo as well.
# LANG=C zypper se -s mozilla-js192 Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository --+---------------+---------+----------------+------+--------------------------------------- v | mozilla-js192 | package | 1.9.2.13-3.1 | i586 | Mozilla based projects (openSUSE_11.1) v | mozilla-js192 | package | 1.9.2.12-0.1.1 | i586 | openSUSE-11.1-Updates v | mozilla-js192 | package | 1.9.2.10-0.4.1 | i586 | openSUSE-11.1-Updates v | mozilla-js192 | package | 1.9.2.8-1.1.1 | i586 | openSUSE-11.1-Updates i | mozilla-js192 | package | 1.9.2.12-1.2 | i586 | (System Packages) There's no such debug package, at least not for 11.1: http://download.opensuse.org/repositories/mozilla/openSUSE_11.1/i586/ Build issue?
BTW, what's up with the buildsymbols packages? A new debug symbols variant?
Yes, but it's not used for local gdb debugging but only for automatic retracing of minidumps sent to crash-reports.mozilla.com
Why am I not surprised, that it crashed somewhere in js (if my analysis is sound), probably because it wrongly does not ignore the SIGPIPE. The question is, what can trigger SIGPIPEs in the JS interpreter?
Would be really interesting to see more symbols here.
Yes, I'm eagerly awaiting the next crash ;-) preferably with the js192 debug packages in place. Pete -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org