I'm trying to debug part of the memory system using the debug callout technique described in the docs. I'm using ddd 3.3.11 on top of gdb 6.4 running on linux/x86_64. m5 runs fine on all my benchmarks outside of the debugger. When running inside gdb, I've placed a breakpoint on MemDebug::cacheAccess as described in the docs and execution halts there but the debugger is unable to tell me very much useful about the contents of the "req" object passed to the callout - the error is "Cannot access memory at address <addr>". Is this an example of the poor support for debugging templated code in gdb? Is there anything I can do to let me probe the req object?
Many Thanks, James -- [EMAIL PROTECTED] http://www.cl.cam.ac.uk/~jrs53/ ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ m5sim-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/m5sim-users
