Locale values ​​in minidump with optimizations enabled

I am working on creating mini disks for my managed application. Here is what I still have:

  • I installed an exception filter, as in this article . In the filter, I call MiniDumpWriteDump.
  • I managed to load the resulting dump in the VS debugger, view the call stack and view the locals values.

However, when optimization is enabled in my project, locals are not available (I get "The value of the local or argument 'x' is unobtainable at this time" ). Now I know why this happens: optimization can do things like reusing locales, which means that the compiled code no longer reflects the source code.

My question is: is there a workaround? Any way to get optimized code and access locals? I do not mind using third-party tools to create / view a mini-drive.

+2
source share

All Articles