LoÃc Minier <[EMAIL PROTECTED]> writes:
> This is a followup on Debian bug <http://bugs.debian.org/285404>.
>
> Juergen Kreileder <[EMAIL PROTECTED]> - Mon, Dec 13, 2004:
>
>> Galeon likes to crash when a link opens a new window. I've seen
>> this happening randomly on sites for some time. Now I found a site
>> where this happens each time:
>> http://secunia.com/multiple_browsers_window_injection_vulnerability_test/
>> When I click on one of the links in 'Step 2', Galeon opens a blank
>> new window and the crashes.
>
> I couldn't reproduce this with latest Galeon on a PPC machine, do
> you still get the crash? If yes, please run Galeon from a terminal
> and tell me whether it "segfaults" (SIGSEGV), or whether you get
> warnings. If you've got some gdb knowledge, I'd be nice to provide
> a stack trace.
I still can reproduce the crash. Interestingly it only happens when
Galeon gets started from the menu or a lauchner on the GNOME panel.
When starting Galeon from an xterm everything works fine.
The crash seems to be JavaScript related:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 24311)]
0x0ddae44c in js_ExecuteRegExp () from /usr/lib/libmozjs.so
(gdb) bt
#0 0x0ddae44c in js_ExecuteRegExp () from /usr/lib/libmozjs.so
#1 0x0ddb96b4 in js_BoyerMooreHorspool () from /usr/lib/libmozjs.so
#2 0x0ddb96b4 in js_BoyerMooreHorspool () from /usr/lib/libmozjs.so
#3 0x0ddb96b4 in js_BoyerMooreHorspool () from /usr/lib/libmozjs.so
#4 0x0ddb96b4 in js_BoyerMooreHorspool () from /usr/lib/libmozjs.so
#5 0x0ddb96b4 in js_BoyerMooreHorspool () from /usr/lib/libmozjs.so
#6 0x0ddb96b4 in js_BoyerMooreHorspool () from /usr/lib/libmozjs.so
#7 0x0ddb96b4 in js_BoyerMooreHorspool () from /usr/lib/libmozjs.so
#8 0x0ddb96b4 in js_BoyerMooreHorspool () from /usr/lib/libmozjs.so
#9 0x0ddb96b4 in js_BoyerMooreHorspool () from /usr/lib/libmozjs.so
#10 0x0ddb96b4 in js_BoyerMooreHorspool () from /usr/lib/libmozjs.so
#11 0x0ddb96b4 in js_BoyerMooreHorspool () from /usr/lib/libmozjs.so
#12 0x0ddb96b4 in js_BoyerMooreHorspool () from /usr/lib/libmozjs.so
#13 0x0ddb96b4 in js_BoyerMooreHorspool () from /usr/lib/libmozjs.so
#14 0x0ddb96b4 in js_BoyerMooreHorspool () from /usr/lib/libmozjs.so
#15 0x0ddb96b4 in js_BoyerMooreHorspool () from /usr/lib/libmozjs.so
#16 0x0ddb96b4 in js_BoyerMooreHorspool () from /usr/lib/libmozjs.so
#17 0x0ddb96b4 in js_BoyerMooreHorspool () from /usr/lib/libmozjs.so
#18 0x0ddb96b4 in js_BoyerMooreHorspool () from /usr/lib/libmozjs.so
#19 0x0ddb96b4 in js_BoyerMooreHorspool () from /usr/lib/libmozjs.so
#20 0x0ddb96b4 in js_BoyerMooreHorspool () from /usr/lib/libmozjs.so
#21 0x0ddb96b4 in js_BoyerMooreHorspool () from /usr/lib/libmozjs.so
#22 0x0ddb96b4 in js_BoyerMooreHorspool () from /usr/lib/libmozjs.so
#23 0x0ddb96b4 in js_BoyerMooreHorspool () from /usr/lib/libmozjs.so
#24 0x0ddb96b4 in js_BoyerMooreHorspool () from /usr/lib/libmozjs.so
Previous frame inner to this frame (corrupt stack?)
(gdb) i th
5 Thread 98308 (LWP 24422) 0x0e3b0888 in nanosleep ()
from /lib/libpthread.so.0
4 Thread 32771 (LWP 24335) 0x0e3b0888 in nanosleep ()
from /lib/libpthread.so.0
3 Thread 16386 (LWP 24318) 0x0e0d1580 in poll () from /lib/libc.so.6
2 Thread 32769 (LWP 24317) 0x0e0d1580 in poll () from /lib/libc.so.6
* 1 Thread 16384 (LWP 24311) 0x0ddae44c in js_ExecuteRegExp ()
from /usr/lib/libmozjs.so
I can't reproduce the problem with Mozilla and Epiphany.
Juergen
--
Juergen Kreileder, Blackdown Java-Linux Team
http://www.blackdown.org/java-linux/java2-status/
