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: Wed, 26 Jan 2011 21:33:52 +0100 [thread overview]
Message-ID: <4D408530.4020100@gmail.com> (raw)
In-Reply-To: <4D4081B5.3090909@twiddle.net>
On 01/26/2011 09:19 PM, Richard Henderson wrote:
> On 01/26/2011 12:17 PM, Lluís wrote:
>> Richard Henderson writes:
>>
>>> On 01/26/2011 03:07 AM, Stefano Bonifazi wrote:
>>>> P.S. Please just answer that last question, whether it is possible to
>>>> have a variable showing the upper bound of heap (some brk_end) for a
>>>> target process
>>> No, the heap grows until it reaches some other memory mapped entity.
>> > From man brk(2) :
>>
>> "sbrk() increments the program's data space by increment bytes.
>> Calling sbrk() with an increment of 0 can be used to find the
>> current location of the program break."
>>
>> I already sent this to the list in a previous mail, but it seems you
>> overlooked it as you were not an explicit recipient.
> That's the current top of the heap. I answered the question as if
> it was asking for the maximum top of the heap.
>
>
> r~
Yup!
I am concerned what can be the highest address used as heap by a target
binary, because I am creating multiple instances of qemu-user, and I
wanna prevent the target process images and heaps to overlap..
Good enough to know the mmu will stop giving memory when meeting another
memory mapped region..
Moreover I think I'd have to call sbrk from within the target binary for
resizing its heap, whereas I wanna control it from qemu-user that is
loading, then translating and executing it..
@Luis: Yup sorry for not answering the previous post of yours, I thought
I'd receive emails always when somebody answered a post I created at the
beginning!
Thank you!
Regards,
Stefano B.
next prev parent reply other threads:[~2011-01-26 20:33 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
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 [this message]
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=4D408530.4020100@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).