From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=39435 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1PhUCy-0000F3-0K
	for qemu-devel@nongnu.org; Mon, 24 Jan 2011 16:44:21 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <stefboombastic@gmail.com>) id 1PhUCv-0005lf-Px
	for qemu-devel@nongnu.org; Mon, 24 Jan 2011 16:44:19 -0500
Received: from mail-ww0-f53.google.com ([74.125.82.53]:36349)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <stefboombastic@gmail.com>) id 1PhUCv-0005lH-LR
	for qemu-devel@nongnu.org; Mon, 24 Jan 2011 16:44:17 -0500
Received: by wwi18 with SMTP id 18so4467879wwi.10
	for <qemu-devel@nongnu.org>; Mon, 24 Jan 2011 13:44:16 -0800 (PST)
Message-ID: <4D3DF2A9.3080609@gmail.com>
Date: Mon, 24 Jan 2011 22:44:09 +0100
From: Stefano Bonifazi <stefboombastic@gmail.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] qemu-user: relocating target code weakness
References: <4D3D63B3.1030402@gmail.com> <4D3DD713.10405@twiddle.net>
In-Reply-To: <4D3DD713.10405@twiddle.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Richard Henderson <rth@twiddle.net>
Cc: QEMU Developers <qemu-devel@nongnu.org>


> 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.