derekbruening
commented
9 years ago From bruen...@google.com on August 10, 2011 08:01:08
as a manual workaround for now, you can use -pauseat* and attach the debugger
Open derekbruening opened 9 years ago
derekbruening
commented
9 years ago From bruen...@google.com on August 10, 2011 08:01:08
as a manual workaround for now, you can use -pauseat* and attach the debugger
derekbruening
commented
9 years ago From bruen...@google.com on August 10, 2011 08:09:51
Status: Duplicate
Mergedinto: 134
derekbruening
commented
9 years ago From bruen...@google.com on May 05, 2014 18:08:37
I'm splitting this out again (from issue #134 ) as the initial dump support will not have minidump support b/c the initial implementation is not working, perhaps due to isolation issues:
*\ TODO CRASH trying to call dbghelp!MiniDumpWriteDump()
Trying to call it from drmem (after adding dr_mcontext_to_context() to DR):
From erikcorry@google.com on August 10, 2011 07:28:03
At the moment it is not possible to see the stack or the heap when an error is reported. It would be useful just to see a hex dump of the top of the stack. Even better would be a minidump of the stack/heap since we already have some tools support for this.
Original issue: http://code.google.com/p/drmemory/issues/detail?id=549