All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Grégoire Sutre" <gregoire.sutre@labri.fr>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Non-static variables and nested function pointers [bug #28392]
Date: Thu, 24 Dec 2009 02:56:56 +0100	[thread overview]
Message-ID: <4B32CA68.6090404@labri.fr> (raw)
In-Reply-To: <alpine.GSO.2.00.0912231416110.12423@oretfbsg.Jrfg.Fha.PBZ>

Seth Goldberg wrote:

>   Your problem is probably lack of executable stack support, or at least 
> you haven't linked your application with a linker mapfile that specifies 
> an executable stack -- the callbacks require the use of trampolines to 
> access local variables, which require an executable stack.

Thanks a lot for your answer ! That explains it :-)

I tried linking with -Wl,-z,execstack, but with no success, even though 
readelf shows a new header with this option:

Type           Offset   VirtAddr   PhysAddr   FileSiz MemSiz  Flg Align
GNU_STACK      0x000000 0x00000000 0x00000000 0x00000 0x00000 RWE 0x4

But the problem may come from NetBSD's default policy of non-executable 
stack on i386 (http://www.netbsd.org/docs/kernel/non-exec.html).

I'll have to dig further...  Thanks again,

Grégoire



  reply	other threads:[~2009-12-24  1:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-23 20:48 Non-static variables and nested function pointers [bug #28392] Grégoire Sutre
2009-12-23 22:17 ` Seth Goldberg
2009-12-24  1:56   ` Grégoire Sutre [this message]
2009-12-24  2:07     ` Seth Goldberg
2009-12-24  3:33       ` Grégoire Sutre
2009-12-24  3:50         ` Seth Goldberg
2009-12-24  3:52         ` Seth Goldberg
2009-12-24 22:12   ` Robert Millan
2009-12-26 18:43     ` Grégoire Sutre

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=4B32CA68.6090404@labri.fr \
    --to=gregoire.sutre@labri.fr \
    --cc=grub-devel@gnu.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.