|
From: Jeremy F. <je...@go...> - 2003-12-18 01:07:34
|
On Wed, 2003-12-17 at 01:52, Josef Weidendorfer wrote: > That's another thing. --tracegen gives me nothing. If I do e.g. "valgrind -- > tool=none --trace-codegen ls &>log", code generation printout in log starts > at 0x81000D10. But I know for sure that my instrumentation is already called > for BB 0x81000C10, as the "mov" at 0x81000C10 calls the cache simulator (seen > when raising verbosity of my tool with --ct-verbose). Eh, are you saying that the --trace-codegen=10001 output only starts after 0x81000D10? I can't see any way in which can not print for early EIPs. BTW, could you also enable the VG_(printf) at the start of VG_(main) just to confirm the initial eip/esp values. > BTW: The auto-generated stage2.lds is working fine here on Suse 9.0. Great. J |