All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: *** stack smashing detected ***: ./firefox-bin terminated
Date: Sun, 09 Aug 2009 10:33:16 -0700	[thread overview]
Message-ID: <4A7F085C.6080204@gmail.com> (raw)
In-Reply-To: <4A7F04B2.5000201@gmail.com>

Robert Hancock wrote:
> On 08/08/2009 04:31 PM, Justin Mattock wrote:
>> 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.
>
> Use nspluginwrapper, then Flash will run in a separate process and it 
> won't crash Firefox when it crashes (which it does fairly regularly).
>
>>
>> should I try firefox about this, or change something in the kernel?
>
> Nothing to do with the kernel, it's glibc's stack corruption detection 
> that's being triggered.
>
Cool thanks for that.

at the moment I was thinking nss, nspr
were the causes since I had not
put them into the system yet.(nor do I really want
to compile that mess).

I'll try nsplugginwrapper  and see what happens.
(and leave the stack protection on).

Justin P. Mattock

  reply	other threads:[~2009-08-09 17:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-08 22:31 *** stack smashing detected ***: ./firefox-bin terminated Justin Mattock
2009-08-09 17:17 ` Robert Hancock
2009-08-09 17:33   ` Justin P. Mattock [this message]
2009-08-09 22:23   ` Justin P. Mattock
2009-08-10  7:12   ` Justin P. Mattock

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A7F085C.6080204@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=hancockrwd@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.