Getting a little further with this. Examining the m5.debug coredump with TotalView (which I've found is much nicer than gdb/ddd for debugging C++), the address which is causing problems is 0x1416e0000 which is exactly the same as brk_point, the "top of the data segment". I guess this leaves two options:
1) The CPU is on the correct path and the address is being flagged as invalid wrongly. Maybe the comparison for validDataAddr in process.hh ought to be <= brk_point rather than < brk_point 2) The CPU is misspeculating and this isn't being picked up. For simplicity's sake, I hope the former is true but I suspect that brk_point is strictly exclusive so it's more likely the latter. Any thoughts? Thanks, James -- [EMAIL PROTECTED] http://www.cl.cam.ac.uk/~jrs53/ ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ m5sim-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/m5sim-users
