All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 2995] -fstack-protector-all causes ssh to SIGSEGV
Date: Wed,  2 Mar 2011 13:51:26 +0000 (UTC)	[thread overview]
Message-ID: <20110302135126.5727A8D3E6@busybox.osuosl.org> (raw)
In-Reply-To: <bug-2995-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=2995

--- Comment #5 from Andrew Beard <abeard@wabtec.com>  ---
I seem to be having the same problem on a proprietary Geode LX board I'm
working with.  I just updated to the 2011.02 and with uclibc 0.9.31 if I enable
stack protection all ssh related executables immediately cause a segfault. 
Disabling stack protection seems to alleviate the problem.

One thing I have found is that this problem does not seem to occur with uclibc
09.32-rc2, though.  With the new release candidate I can enable or disable
stack protection without causing a problem.  At this point we're still trying
to decide if we'd rather continue with a pre-release c library or without stack
protection.

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

  parent reply	other threads:[~2011-03-02 13:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-20 15:43 [Buildroot] [Bug 2995] New: -fstack-protector-all causes ssh to SIGSEGV bugzilla at busybox.net
2010-12-20 15:56 ` [Buildroot] [Bug 2995] " bugzilla at busybox.net
2010-12-20 16:52 ` bugzilla at busybox.net
2010-12-20 16:56 ` bugzilla at busybox.net
2010-12-20 21:01 ` bugzilla at busybox.net
2011-03-02 13:51 ` bugzilla at busybox.net [this message]
2011-03-02 14:35 ` bugzilla at busybox.net
2011-09-18 10:18 ` bugzilla at busybox.net
2013-11-28 17:15 ` bugzilla at busybox.net

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=20110302135126.5727A8D3E6@busybox.osuosl.org \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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.