qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefano Bonifazi <stefboombastic@gmail.com>
To: Richard Henderson <rth@twiddle.net>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] qemu-user: relocating target code weakness
Date: Mon, 24 Jan 2011 22:44:09 +0100	[thread overview]
Message-ID: <4D3DF2A9.3080609@gmail.com> (raw)
In-Reply-To: <4D3DD713.10405@twiddle.net>


> Yes.  Have a look at
>
>    http://lists.gnu.org/archive/html/qemu-devel/2010-07/msg01626.html
>
> where I tried to clean this up last year.  The patch never got properly
> reviewed, however.
>
> All that said, unless you have an executable that's been properly
> prepared for relocation, e.g. an ET_DYN binary instead of a normal
> ET_EXEC binary, you will *not* have enough information to do what
> you're suggesting.
>
>
> r~
Wow wonderful! So you fixed the code for PIC (ET_DYN) support? I won't 
have any problem in producing the target code into pie format, as I am 
writing, compiling and linking my target code by my own ;)
A noob question, how can I get your sources? Is there a simpler solution 
than "copy&paste" all the code from your messages into patches and then 
applying them? Can you just send your sources by email? Or can I 
download them from a site?
I am very eager to study your code and to try it :)
Thank you very much!!
Stefano B.

  reply	other threads:[~2011-01-24 21:44 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-24 11:34 [Qemu-devel] qemu-user: relocating target code weakness Stefano Bonifazi
2011-01-24 16:29 ` Mulyadi Santosa
2011-01-24 18:16   ` Stefano Bonifazi
2011-01-24 20:00     ` Mike Frysinger
2011-01-24 20:58       ` Stefano Bonifazi
2011-01-24 21:21         ` Mike Frysinger
2011-01-24 21:52           ` Stefano Bonifazi
2011-01-24 22:11             ` Mike Frysinger
2011-01-24 22:24               ` Stefano Bonifazi
2011-01-24 22:34                 ` Mike Frysinger
2011-01-25  0:06   ` Mike Frysinger
2011-01-25  0:18     ` Mike Frysinger
2011-01-25  8:49       ` Stefano Bonifazi
2011-01-25  8:26     ` Stefano Bonifazi
2011-01-24 19:46 ` Richard Henderson
2011-01-24 21:44   ` Stefano Bonifazi [this message]
2011-01-24 23:32     ` Mike Frysinger
2011-01-25  8:25       ` Stefano Bonifazi
2011-01-25  1:36     ` Richard Henderson
2011-01-25  8:47       ` Stefano Bonifazi
2011-01-25  8:53         ` Mike Frysinger
2011-01-25  9:58           ` Stefano Bonifazi
2011-01-25 10:47           ` Stefano Bonifazi
2011-01-25 16:22             ` Richard Henderson
2011-01-25 19:03               ` Stefano Bonifazi
2011-01-25 11:06           ` Stefano Bonifazi
2011-01-25 16:26             ` Richard Henderson
2011-01-25 19:49               ` Stefano Bonifazi
2011-01-25 20:53                 ` Lluís
2011-01-26 11:07       ` Stefano Bonifazi
2011-01-26 15:38         ` Richard Henderson
2011-01-26 17:44           ` Stefano Bonifazi
2011-01-26 20:17           ` Lluís
2011-01-26 20:19             ` Richard Henderson
2011-01-26 20:33               ` Stefano Bonifazi
2011-01-26 20:36               ` Lluís

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=4D3DF2A9.3080609@gmail.com \
    --to=stefboombastic@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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 NNTP newsgroup(s).