*** stack smashing detected ***: ./firefox-bin terminated

[Justin Mattock]

How should I handle this:

*** stack smashing detected ***: ./firefox-bin terminated
======= Backtrace: =========
/lib64/libc.so.6(__fortify_fail+0x37)[0x7f765ab2a477]
/lib64/libc.so.6(__fortify_fail+0x0)[0x7f765ab2a440]
/home/name/LFS/net/firefox/plugins/libflashplayer.so[0x7f7646911a6f]
/home/name/LFS/net/firefox/plugins/libflashplayer.so[0x7f764690d67c]
/home/name/LFS/net/firefox/plugins/libflashplayer.so[0x7f764691077f]
/home/name/LFS/net/firefox/plugins/libflashplayer.so[0x7f76469090cd]
/home/name/LFS/net/firefox/plugins/libflashplayer.so[0x7f76466f95e0]
/home/name/LFS/net/firefox/plugins/libflashplayer.so[0x7f76466f9c1d]
/home/name/LFS/net/firefox/plugins/libflashplayer.so[0x7f76466bd944]
/home/name/LFS/net/firefox/plugins/libflashplayer.so[0x7f76466c738b]
/home/name/LFS/net/firefox/plugins/libflashplayer.so[0x7f76466af3e1]
/home/name/LFS/net/firefox/plugins/libflashplayer.so[0x7f76466a4af0]
/home/name/LFS/net/firefox/plugins/libflashplayer.so[0x7f764638ed29]
/home/name/LFS/net/firefox/plugins/libflashplayer.so[0x7f764637edaf]
/usr/lib64/libglib-2.0.so.0[0x7f765bbd477b]
/usr/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x22e)[0x7f765bbd320e]
/usr/lib64/libglib-2.0.so.0[0x7f765bbd3958]
/usr/lib64/libglib-2.0.so.0(g_main_context_iteration+0x70)[0x7f765bbd3b40]
./libxul.so[0x7f765efd07a1]
./libxul.so[0x7f765efd0b71]
./libxul.so[0x7f765f08ea79]
./libxul.so[0x7f765f0628bd]
./libxul.so[0x7f765efd0883]
./libxul.so[0x7f765eeaadaf]
./libxul.so(XRE_main+0x213f)[0x7f765e812149]
./firefox-bin[0x401bc0]
/lib64/libc.so.6(__libc_start_main+0xec)[0x7f765aa65a4c]
./firefox-bin[0x4019b9]

even if I move the firefox package to /usr/lib64
this still occurs.

I would like to keep stack protection,
but having firefox crash over any flash content
is unattractive.

should I try firefox about this, or change something in the kernel?


-- 
Justin P. Mattock
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/