From: "Tibor Kircsi" <tkircsi@gmail.com>
To: Frank Kotler <fbkotler@verizon.net>
Cc: linux-assembly@vger.kernel.org
Subject: Re: Current break round up
Date: Wed, 1 Oct 2008 16:40:42 +0200 [thread overview]
Message-ID: <c12f7eca0810010740q2836fe8fi9142a1aad59cbbd@mail.gmail.com> (raw)
In-Reply-To: <48E37E93.3080101@verizon.net>
Hi,
You're right! I tested it and I could write and read above the current
break after I call brk. I'll will test the page border too. Thanks.
regards,
Tibor
On Wed, Oct 1, 2008 at 3:43 PM, Frank Kotler <fbkotler@verizon.net> wrote:
>
> Kircsi Tibor wrote:
>>
>> Hi,
>>
>> Sorry for my english. I started learn assembly again after 15 years.
>> Now, I'm learning about memory management and sys_brk system call. I've
>> created a really simple program, which try to extend the heap size. I've
>> read, when sys_brk is called with the new break address(last usable
>> address of the heap or data segment), it will be rounded up to the next
>> nearest page, but it didn't. Am I misundestand somthing?
>
> I've noticed this. Seems to be related to kernel version (2.4.33.3 here). May be a "bug"? I think you can access memory up to the top of the page (what you/we would "expect" brk to return). I don't know what to make of it.
>
> Best,
> Frank
>
next prev parent reply other threads:[~2008-10-01 14:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 19:26 Current break round up Kircsi Tibor
2008-10-01 13:43 ` Frank Kotler
2008-10-01 14:40 ` Tibor Kircsi [this message]
[not found] ` <61990392562924881677723846250054653396-Webmail2@me.com>
2008-10-01 18:22 ` Frank Kotler
2008-10-01 19:03 ` Kircsi Tibor
2008-10-01 20:27 ` Frank Kotler
2008-10-02 7:27 ` Tibor Kircsi
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=c12f7eca0810010740q2836fe8fi9142a1aad59cbbd@mail.gmail.com \
--to=tkircsi@gmail.com \
--cc=fbkotler@verizon.net \
--cc=linux-assembly@vger.kernel.org \
/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