|Reg. Stack allocation and profiling tools in X86 firstname.lastname@example.org (Subramanian Ramaswamy) (2004-09-13)|
|Re: Reg. Stack allocation and profiling tools in X86 email@example.com (Ian Rogers) (2004-09-14)|
|From:||Ian Rogers <firstname.lastname@example.org>|
|Date:||14 Sep 2004 16:56:59 -0400|
|Organization:||Dept of Computer Science, University of Manchester, U.K.|
|Posted-Date:||14 Sep 2004 16:56:59 EDT|
You can watch the memory allocated to a process in
"/proc/<process_id>/maps" on Linux. X86 stacks grow down and the heap
(top of bss - set by brk) grows up. You also have mmap, which is used to
allocate arbitrary pages of memory.
Subramanian Ramaswamy wrote:
> How is the heap and stack size allocated in X86? Do they start off at
> both ends and keep coming towards each other as they grow as in MIPS?
> If it is like above, is there any profiling tool that will help me
> figure out the maximum stack size for benchmarks on X86, so I can filter
> out all the stack references from the memory trace I plan to generate.
> [It varies from one operating system to another. -John]
Return to the
Search the comp.compilers archives again.