From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tristan Gingold <gingold@adacore.com>
Cc: Daniel Jacobowitz <dan@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: Regression on prelinked-sepdebug-shlibs
Date: Thu, 07 Jan 2010 11:10:00 -0000 [thread overview]
Message-ID: <20100107110927.GA28546@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <C631324A-A21F-4E14-B0D1-7F3A114E7DE9@adacore.com>
On Thu, 07 Jan 2010 12:03:04 +0100, Tristan Gingold wrote:
...
> I am not sure that you can create a linux native executable with a section whose vma is 0.
> But unfortunately linux refuses to execute that (I got a sigkill very very
> early) so I can't play with that.
https://bugzilla.redhat.com/show_bug.cgi?id=434714
From Chuck Ebbert:
echo "0" >/proc/sys/vm/mmap_min_addr
That should fix it -- at least on F8 changing that from 0 to 32768 made it fail.
(The executable code starts at 0.)
From Roland McGrath:
Yup, I think this is pretty much expected behavior.
i.e. an ET_EXEC with a p_vaddr at 0 is asking for a mmap that it is often
security policy to refuse. Unfortunately there really isn't much better than
SIGKILL death that you can expect for this.
Regards,
Jan
next prev parent reply other threads:[~2010-01-07 11:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-25 20:05 Jan Kratochvil
2010-01-04 9:50 ` Tristan Gingold
2010-01-04 10:24 ` Jan Kratochvil
2010-01-04 11:54 ` Tristan Gingold
2010-01-04 15:22 ` Tristan Gingold
2010-01-04 18:10 ` Jan Kratochvil
2010-01-05 11:02 ` Tristan Gingold
2010-01-05 16:15 ` Jan Kratochvil
2010-01-06 11:20 ` Tristan Gingold
2010-01-06 16:38 ` Tristan Gingold
2010-01-06 18:05 ` Jan Kratochvil
2010-01-06 19:16 ` Daniel Jacobowitz
2010-01-07 11:02 ` Tristan Gingold
2010-01-07 11:10 ` Jan Kratochvil [this message]
2010-01-07 11:18 ` Tristan Gingold
2010-01-07 13:42 ` Daniel Jacobowitz
2010-01-07 14:21 ` Tristan Gingold
2010-01-07 14:26 ` Daniel Jacobowitz
2010-01-07 14:37 ` Tristan Gingold
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=20100107110927.GA28546@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=dan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=gingold@adacore.com \
/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