In case anyone is still having trouble with this You can use gdb to set a breakpoint inside of that routine, and then use the backtrace gdb command to find out which function called traceInst()
$ gdb build/ARM/gem5.opt (gdb) breakpoint exetrace.cc:line_number (gdb) run ... Then when (if) it hits the breakpoint (gdb) backtrace On Thu, May 23, 2013 at 10:29 PM, Yanqi Zhou <yan...@princeton.edu> wrote: > Hi Everyone, > I have a question about the trace files. > In src/cpu/exetrace.cc, there is a > Trace::ExeTracerRecord::traceInst(StaticInstPtr inst, bool ran) > I know this function is used to print out the trace, but I searched > everywhere, could not find where it is used. I need to know where it is > used because I need to build an interface between gem5 and my own simulator > so that instead of using the trace to drive my simulator, I can directly > feed the trace to my simulator. > Can anyone help me with this problem? > > Thanks, > > _______________________________________________ > gem5-users mailing list > gem5-users@gem5.org > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users > -- Martin
_______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
