Show all memory occupied by the program

[Ravi]

Can you all please suggest a program which tell us the range of memry
addresses occupied by the given c program?

[Keith Thompson]

Ravi <ra*********@gm ail.comwrites:

Can you all please suggest a program which tell us the range of memry
addresses occupied by the given c program?

It can't be done in portable standard C. Try asking in a newsgroup
that deals with your operating system.

--
Keith Thompson (The_Other_Keit h) ks***@mib.org <http://www.ghoti.net/~kst>
San Diego Supercomputer Center <* <http://users.sdsc.edu/~kst>
"We must do something. This is something. Therefore, we must do this."
-- Antony Jay and Jonathan Lynn, "Yes Minister"

[Walter Roberson]

In article <11************ **********@j4g2 000prf.googlegr oups.com>,
Ravi <ra*********@gm ail.comwrote:

>Can you all please suggest a program which tell us the range of memry
addresses occupied by the given c program?

gmemusage

http://techpubs.sgi.com/library/tpl/...t1/gmemusage.z

It is SGI IRIX specific, but you just asked for *a* program, without
indicating anything about the operating systems that are useful
for your purposes.

There is absolutely no way to get information about memory address
ranges through pure C, and it seems highly unlikely that such
a facility would ever be added to C; for one thing, it's kinda
difficult to define what the address ranges should mean for embedded
systems. Information about memory address ranges is inherently system
specific, so you will need to continue your investigations in a
newsgroup that deals with your operating system.

--
"No one has the right to destroy another person's belief by
demanding empirical evidence." -- Ann Landers

[CBFalconer]

Ravi wrote:

>
Can you all please suggest a program which tell us the range of
memry addresses occupied by the given c program?

No. Off-topic.

--
<http://www.cs.auckland .ac.nz/~pgut001/pubs/vista_cost.txt>
<http://www.securityfoc us.com/columnists/423>
<http://www.aaxnet.com/editor/edit043.html>
<http://kadaitcha.cx/vista/dogsbreakfast/index.html>
cbfalconer at maineline dot net

--
Posted via a free Usenet account from http://www.teranews.com

[Chris Hills]

In article <11************ **********@j4g2 000prf.googlegr oups.com>, Ravi
<ra*********@gm ail.comwrites

>Can you all please suggest a program which tell us the range of memry
addresses occupied by the given c program?

Try looking at the map file that is output by the compiler.

Ignore the netpolice.
--
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
\/\/\/\/\ Chris Hills Staffs England /\/\/\/\/
/\/\/ ch***@phaedsys. org www.phaedsys.org \/\/\
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/

[Chris Hills]

In article <ln************ @nuthaus.mib.or g>, Keith Thompson
<ks***@mib.orgw rites

>Ravi <ra*********@gm ail.comwrites:

>Can you all please suggest a program which tell us the range of memry
addresses occupied by the given c program?

It can't be done in portable standard C. Try asking in a newsgroup
that deals with your operating system.

It has nothing to do with the OS it sounds like he is looking for the
map file that the compiler will output.

--
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\
\/\/\/\/\ Chris Hills Staffs England /\/\/\/\/
/\/\/ ch***@phaedsys. org www.phaedsys.org \/\/\
\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/

[Walter Roberson]

In article <qs************ **@phaedsys.dem on.co.uk>,
Chris Hills <ch***@phaedsys .demon.co.ukwro te:

>In article <11************ **********@j4g2 000prf.googlegr oups.com>, Ravi
<ra*********@g mail.comwrites

>>Can you all please suggest a program which tell us the range of memry
addresses occupied by the given c program?

>Try looking at the map file that is output by the compiler.

*What* map file output by the compiler? The compilers I use
(brand name compilers) don't output a map file; the toolsets
include tools to -generate- various forms of memory summaries,
but the compilers don't output memory maps.

Even the advice to look at map files is system specific.
--
All is vanity. -- Ecclesiastes

[Martin Ambuhl]

Chris Hills wrote:

In article <ln************ @nuthaus.mib.or g>, Keith Thompson
<ks***@mib.orgw rites

>Ravi <ra*********@gm ail.comwrites:

>>Can you all please suggest a program which tell us the range of memry
addresses occupied by the given c program?

It can't be done in portable standard C. Try asking in a newsgroup
that deals with your operating system.

It has nothing to do with the OS it sounds like he is looking for the
map file that the compiler will output.

That is, of course, absurd. The output of the compiler tells you
*nothing* about the memory addresses used by the program.

[Martin Ambuhl]

Chris Hills wrote:

In article <11************ **********@j4g2 000prf.googlegr oups.com>, Ravi
<ra*********@gm ail.comwrites

>Can you all please suggest a program which tell us the range of memry
addresses occupied by the given c program?

Try looking at the map file that is output by the compiler.

That is, of course, absurd. The output of the compiler tells you
*nothing* about the memory addresses used by the program.

>
Ignore the netpolice.

More important is to ignore Chris Hills, who obviously knows nothing.

[Walter Roberson]

In article <js************ **@phaedsys.dem on.co.uk>,
Chris Hills <ch***@phaedsys .demon.co.ukwro te:

>In article <ln************ @nuthaus.mib.or g>, Keith Thompson
<ks***@mib.org writes

>>Ravi <ra*********@gm ail.comwrites:

>>Can you all please suggest a program which tell us the range of memry
addresses occupied by the given c program?

>>It can't be done in portable standard C. Try asking in a newsgroup
that deals with your operating system.

>It has nothing to do with the OS it sounds like he is looking for the
map file that the compiler will output.

Chris, I was really convinced that you knew better than that.

The OP's question is completely meaningless on some operating systems,
and on some other operating systems none of the major compilers generate
memory maps (though other tools might be able to generate them.)

The question is also not specific enough to be answerable by the
"memory map" pancea. If for a particular program, some of the
variables are tossed into a section marked as Demand Zero Paging,
an other variables are tossed into a section for Block Initialize Data,
and some of the code is put down below the 64K boundary so short addresses
can be used, and if there are unusued gaps between each of these, then
does the OP need to know the start and end of each and every used segment?
If there happen to be 5 unused bytes between the code for one function
and the code for another, is that detail required to be revealed, since
those 5 bytes are -not- part of the range of memory addresses
occupied by that program? Does the OP need to know where each DLL
or DSO will get mapped into in virtual address space? If the OP is
using a malloc that uses mmap() to bring pages into the virtual address
range then the mmap() could "fill in" any space not nailed down, in
which case the "range of memory addressed occupied by the given c program"
could only be determined by -running- the program.
--
"No one has the right to destroy another person's belief by
demanding empirical evidence." -- Ann Landers