Just want to add another bit of information. When I changed:
.
.
.
.
.
.
frame was correct when destructing my local STL string 'x'.
Compiler: Visual Studio .NET 2003 (13.10.3077)
Command line options:
/O2 /D "WIN32" /D "NDEBUG" /D "_LIB" /D "_ATL_ATTRIBUTES" /D "_MBCS" /FD
/EHsc /MT /GS /GR /Yu"stdafx.h" /W3 /c /Wp64 /Zi /TP
CRT: static lib
OS: Windows 2003 Enterprise Server SP1
Threads: Well the app for the most part is single threaded, though there are
multiple threads running (we have a thread doing heartbeat, one watching a
settings file for changes, etc.)
Repro: I've been working on a simpler repro but have not yet produced one.
--
Thanks,
Nick
"Carl Daniel [VC++ MVP]" wrote:
nickdu wrote:
I'm tracking down a problem where we're running into an access
violation while unwinding the stack after throwing a C++ exception.
From my investigation it appears the stack frame is not correctly
setup. Below is an example of what I've observed.
A few more basic questions:
What compiler version are you using? What command line options? Which CRT
version? Which OS? Are there multiple threads involved?
And the biggie - Can you produce a small but complete program that
reproduces the problem (or does this only happen in a gigantic application)?
-cd