From: Stefano Bonifazi <stefboombastic@gmail.com>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] qemu-user: relocating target code weakness
Date: Tue, 25 Jan 2011 12:06:17 +0100 [thread overview]
Message-ID: <4D3EAEA9.5050302@gmail.com> (raw)
In-Reply-To: <AANLkTin39Aa8tOUm2guHYLr734n60W+SB=KWoZnRp4VJ@mail.gmail.com>
On 01/25/2011 09:53 AM, Mike Frysinger wrote:
> On Tue, Jan 25, 2011 at 03:47, Stefano Bonifazi wrote:
>> On 01/25/2011 02:36 AM, Richard Henderson wrote:
>>> On 01/24/2011 01:44 PM, Stefano Bonifazi wrote:
>>>> Wow wonderful! So you fixed the code for PIC (ET_DYN) support?
>>> Yes.
>>>
>>>> how can I get your sources?
>>> I was mistaken -- a later version of the patch set was in fact merged.
>>> I simply forgot to delete my working branch afterward.
>> Sorry.. merged with qemu? What version? I have qemu.0.13.0 and there are no
>> your fixes..
>> How can I get the fixed qemu sources?
> you probably want to use the latest git tree
> http://git.qemu.org/qemu.git/
> -mike
Hi again! :)
debugging a test pie code using qemu-ppc with your (and my little one)
fixes I got this:
> start_brk 0x00000000
> end_code 0x400102e0
> start_code 0x40000000
> start_data 0x4001024c
> end_data 0x400102e0
> start_stack 0x40811438
> brk 0x400102e4
> entry 0x40828c24
that is start_brk is 0
As far as I understood brk is the .bss section, that is unitialized data
area, am I right?
If not pls could you be so kind to explain me what it is, or pointing me
to some document where it is explained.. among all material I am
studying about linkers, relocations, I never found brk other than in qemu..
Once i am sure what it is I'll try to fix (if needed.. for me it is too
strange it is zero) it..
Thank you again!
Stefano B.
next prev parent reply other threads:[~2011-01-25 11:06 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
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 [this message]
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=4D3EAEA9.5050302@gmail.com \
--to=stefboombastic@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=vapier.adi@gmail.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;
as well as URLs for NNTP newsgroup(s).