From: Andreas Schwab <schwab@linux-m68k.org>
To: Paul Brook <paul@codesourcery.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
riku.voipio@iki.fi, Alexander Graf <agraf@suse.de>,
"Bernhard M. Wiedemann" <bwiedemann@suse.de>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] ARM brk bug
Date: Sat, 03 Mar 2012 23:08:59 +0100 [thread overview]
Message-ID: <m24nu5e3r8.fsf@igel.home> (raw)
In-Reply-To: <201203032117.39190.paul@codesourcery.com> (Paul Brook's message of "Sat, 3 Mar 2012 21:17:37 +0000")
Paul Brook <paul@codesourcery.com> writes:
>> 15545 brk(NULL) = 0x00012000
>> 15545 brk(0x00812000) = 0x00012000
>
> This is your bug. According to the trace above, the brk call fails, but
> returns success anyway. A quick look at do_brk confirms this suspicion.
This is not a bug. The brk syscall always returns the break value,
either the new one (on success) or the current one (on failure).
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2012-03-03 22:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 15:16 [Qemu-devel] ARM brk bug Bernhard M. Wiedemann
2012-02-27 15:32 ` Peter Maydell
2012-02-27 17:03 ` Bernhard M. Wiedemann
2012-02-27 17:04 ` Peter Maydell
2012-03-02 17:49 ` Peter Maydell
2012-03-03 1:42 ` Alexander Graf
2012-03-03 21:02 ` Alexander Graf
2012-03-03 21:05 ` Alexander Graf
2012-03-03 21:17 ` Paul Brook
2012-03-03 22:08 ` Andreas Schwab [this message]
2012-03-03 21:23 ` malc
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=m24nu5e3r8.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=agraf@suse.de \
--cc=bwiedemann@suse.de \
--cc=paul@codesourcery.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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).