public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: John Dallaway <john@dallaway.org.uk>
To: Rutger Hofman <rutger@cs.vu.nl>
Cc: eCos development list <ecos-devel@ecos.sourceware.org>
Subject: GCC stack protector with linux synthetic target
Date: Mon, 29 Jun 2009 07:24:00 -0000	[thread overview]
Message-ID: <4A486BEE.9070803@dallaway.org.uk> (raw)
In-Reply-To: <4A475994.7010203@cs.vu.nl>

Hi Rutger

Rutger Hofman wrote:

> An aside: I run Ubuntu. At first, I couldn't run synth at all.
> Applications would crash, and gdb would crash on the application too!
> After some list searching, I found out that this probably is
> Ubuntu-specific. We need to include -fno-stack-protector in the
> GLOBAL_CFLAGS configure flag. Request: cannot this be automated for
> synth building? My guess is that it will not harm on systems other than
> Ubuntu, and it will save Ubuntu users effort.

Do you understand _why_ eCos is crashing with the GCC stack protector
enabled? Is it due to an assumption made in eCos regarding the stack
frame which could be corrected? We should ensure we understand the
nature of the failure before disabling this feature.

John Dallaway

  parent reply	other threads:[~2009-06-29  7:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-28 11:46 Rutger's NAND flash now has a synth package Rutger Hofman
2009-06-29  6:42 ` Simon Kallweit
2009-06-29  7:52   ` Sergei Gavrikov
2009-06-29 11:32   ` Rutger Hofman
2009-06-29  7:24 ` John Dallaway [this message]
2009-06-29  7:50   ` GCC stack protector with linux synthetic target Andrew Lunn
2009-06-29  9:50   ` Bart Veer
2009-06-30  8:55     ` John Dallaway

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=4A486BEE.9070803@dallaway.org.uk \
    --to=john@dallaway.org.uk \
    --cc=ecos-devel@ecos.sourceware.org \
    --cc=rutger@cs.vu.nl \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).