On Mon, Jan 10, 2011 at 1:12 AM, sunil shah <[email protected]>wrote:
> Hi, > > I want to get the virtual address trace of x86 instruction executed. > > By default Marss provides a way to generate an execution trace. In 'ptlsim.h' file, un-comment the '#define TRACE_RIP' and recompile. This will enable capturing trace of executed instructions in file 'ptl_rip_trace'. Note: If you run for long time this fill will eat up all hard-disk space. I tried using in *ReorderBufferEntry::commit()* function field, *uop.rip.rip > * field is giving some address but the obtained address is not same at the > virtual address of instruction which I obtained by using objdump to > disassemble the executable I am running. > > That is interesting. At what point are you switching from emulation to simulation? If you are using 'start_sim' tool then it takes about 1 million instructions to complete and start the next process. Also take a look at this python script ( https://github.com/downloads/avadhpatel/marss/trace_to_func.py) that helps in mapping RIP address to function of your benchmark/application. - Avadh > Any help will be highly appreciated. > Thanks in anticipation > > Regards > Sunil Shah > School of Computing > NUS > Singapore > > > _______________________________________________ > http://www.marss86.org > Marss86-Devel mailing list > [email protected] > https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel > >
_______________________________________________ http://www.marss86.org Marss86-Devel mailing list [email protected] https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel
