I'm sorry, I did not mean to be so unspecific. When running the simulation using ./build/ALPHA_SE/m5.fast I have been able to find the specific virtual address in memory when a load or store is committed by modifying a few lines in src/cpu/o3/lsq_unit_impl.hh
The difficulty I'm encountering now is identifying each virtual address to the stack or the heap. That is why I'm interested in the ending address of the stack and how to keep tack of it during simulation as it grows. Is there a file where the Stack information is defined, or kept during simulation. Sorry for being so unspecific before, and please let me know if more information is needed. Thanks Simon On Wed, Jun 13, 2012 at 1:16 PM, Jack Harvard <[email protected]>wrote: > Your question is not specific enough, bare-metal or OS, X86 or ARM > architecture, for example, ARM provides a register indicating the > Stack Pointer (r13). In Linux, you can cat /proc/pid/maps to get per > process info on stack and heap. > > Jack Harvard > > > On Wed, Jun 13, 2012 at 5:01 PM, Simon Garcia de Gonzalo > <[email protected]> wrote: > > Is there a way to keep track of the size of the stack? For example, what > > address does the stack starts and ends and where does the heap starts? > > > > Thanks > > Simon > > > > _______________________________________________ > > gem5-users mailing list > > [email protected] > > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users > _______________________________________________ > gem5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users >
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
