From: Jon DeVree <jadevree@mtu.edu>
To: linux mailing-list <linux-kernel@vger.kernel.org>
Subject: Re: How to determine the start of DATA segment
Date: Thu, 30 Mar 2006 11:52:25 -0500 [thread overview]
Message-ID: <20060330165225.GA24074@tesla.setec> (raw)
In-Reply-To: <728201270603300837g60eefb65u8b55df910b86f6c4@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 542 bytes --]
On Thu, Mar 30, 2006 at 10:37:25AM -0600, Ram Gupta wrote:
> Is there a system call or library function which a process can use to
> determine the start of its data segment . I need to know the start of
> the data segment so that process does not cross its DATA limit. Using
> this information & sbrk it knows how much data space is already used &
> how much it can grow further without crossing the limit.
I think getrlimit() might be what you are looking for.
--
Jon
"RISC architecture is gonna change everything." -Kate Libby
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
next prev parent reply other threads:[~2006-03-30 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-30 16:37 How to determine the start of DATA segment Ram Gupta
2006-03-30 16:52 ` Jon DeVree [this message]
2006-03-30 17:12 ` Ram Gupta
2006-03-30 17:31 ` Phillip Susi
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=20060330165225.GA24074@tesla.setec \
--to=jadevree@mtu.edu \
--cc=linux-kernel@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