From: Chuck Ebbert <cebbert@redhat.com>
To: Ulrich Kunitz <kune@deine-taler.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org, honza@jikos.cz, jkosina@suse.cz
Subject: Re: Is PIE randomization breaking klibc binaries?
Date: Tue, 24 Jul 2007 18:41:07 -0400 [thread overview]
Message-ID: <46A68003.6060901@redhat.com> (raw)
In-Reply-To: <20070724220053.GA20531@deine-taler.de>
On 07/24/2007 06:00 PM, Ulrich Kunitz wrote:
> On 07-07-24 16:57 Chuck Ebbert wrote:
>
>>> $ strace ./cat
>>> execve("./cat", ["./cat"], [/* 55 vars */]) = -1 ENOENT (No such file or directory)
>>> ...
>
> Chuck, my binaries run always into a segmentation violation. So
> ENOENT is not the issue. (Notify it was on an x86-64.)
>
Okay, I tested with Fedora on x86_64 and it worked there too.
(Not that that proves much.)
Did you capture any of the error messages, like the address
of the segfault?
next prev parent reply other threads:[~2007-07-24 22:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-20 21:13 Is PIE randomization breaking klibc binaries? Ulrich Kunitz
2007-07-20 22:05 ` H. Peter Anvin
2007-07-24 20:34 ` Chuck Ebbert
2007-07-24 20:57 ` Chuck Ebbert
2007-07-24 22:00 ` Ulrich Kunitz
2007-07-24 22:41 ` Chuck Ebbert [this message]
2007-07-24 22:45 ` H. Peter Anvin
2007-07-24 23:13 ` Ulrich Kunitz
2007-07-25 6:32 ` Ulrich Kunitz
2007-07-31 11:30 ` Jiri Kosina
2007-07-31 12:01 ` H. Peter Anvin
2007-07-31 12:19 ` Jiri Kosina
2007-07-31 12:15 ` H. Peter Anvin
2007-08-01 14:07 ` Jiri Kosina
2007-08-02 4:29 ` Ulrich Kunitz
2007-08-02 11:21 ` Jiri Kosina
2007-08-02 17:03 ` Bret Towe
2007-08-02 19:02 ` Sergey Vlasov
2007-08-02 19:10 ` H. Peter Anvin
2007-08-02 20:42 ` Ulrich Kunitz
2007-08-02 21:03 ` Jiri Kosina
2007-08-02 19:10 ` Ulrich Kunitz
2007-07-21 6:02 ` Bret Towe
2007-07-21 10:18 ` Andrew Morton
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=46A68003.6060901@redhat.com \
--to=cebbert@redhat.com \
--cc=honza@jikos.cz \
--cc=hpa@zytor.com \
--cc=jkosina@suse.cz \
--cc=kune@deine-taler.de \
--cc=linux-kernel@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