Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: Dave Platt <dplatt@radagast.org>
To: linux-hams <linux-hams@vger.kernel.org>
Subject: Re: Ubuntu 8.04 / 8.10
Date: Fri, 13 Feb 2009 13:39:33 -0800	[thread overview]
Message-ID: <4995E895.10701@radagast.org> (raw)
In-Reply-To: <4995DEA5.7000203@exemail.com.au>

Ray Wells wrote:
> Peter,
> 
> This problem arose with fbb around kernel 2.6.20 (can't remember just 
> which one now)
> 
> The fix I apply is to compile fbb with  -fno-stack-protection added to 
> its Makefile. I don't have a fix if you install fbb from a deb package.
> 
> It seems that stack protection was included in kernels as a security 
> plug for stack overflow.
> 
> I sent quite a bit about this to the xfbb list around 18 months ago.

The real question (to me at least) is whether the stack-smash abort
is a false alarm, or whether it indicates a real problem in the
FBB software.

If there really is a way in which the FBB software is managing to
smash its own stack (via e.g. a buffer that's too small, indexing
out of bounds, etc.), then simply disabling the stack protection
feature via recompilation is a bit like replacing a blown fuse
with a larger one.  You may get away with it, or it may burn your
house down :-(

It'd probably be necessary to compile xfbb with -g and run it
under GDB or a similar debugger, and investigate the state of the
stack at the time of the abort, to figure out what's being
over-written.

  reply	other threads:[~2009-02-13 21:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-13 11:15 Ubuntu 8.04 / 8.10 Peter Mallett
2009-02-13 17:34 ` John Ronan
2009-02-13 20:57 ` Ray Wells
2009-02-13 21:39   ` Dave Platt [this message]
2009-02-13 22:30     ` Curt, WE7U
2009-02-13 22:32     ` Ray Wells

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=4995E895.10701@radagast.org \
    --to=dplatt@radagast.org \
    --cc=linux-hams@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox