Wrong exception location in minidump about crashrpt HOT 8 CLOSED

Here's the code.

Forget to mention, if pszDebugHelpDLL is NULL (as CrashRptTest shows), even
dbghelp.dll is in the System32 directory (shipped with Windows 7), the minidump 
are
not generated (the LoadLibrary at line 331 returns NULL). If I copy dbghelp.dll 
to
the same directory as CrashSender.exe, everything is OK.

Please create new issue per each detected bug. It will simplify tracking 
changes. 

As you wish.

I managed to discover that the Debug configuration works fine. Then I narrow 
down the
difference from the Release configuration, and found that if any optimization is
turned on (other than /Od), the location was wrong. Is this a known issue? The
performance might deteriorate tremendously if optimizations are forced to 
disable,
and force me to release a debug version separately.

BugTrap has the same behavior.

So, the reason is in optimizations? Not in CrashRpt bug? If so, there is 
nothing to
fix here.

I suppose optimizations really can affect the minidump generation. For example, 
if
you try to debug the Release build in Visual Studio, you can see that 
optimizations
affect the accuracy of the debugger. The same way the optimizations may affect 
the
minidump.

The problem seems to be caused by program optimizations, not by bug in 
CrashRpt.