Odd Crash that only happens in Visual Studio C++ 2008 Release.

EDN Admin

Well-known member
Joined
Aug 7, 2010
Messages
12,794
Location
In the Machine
Here is the stack trace:<br/>
<div style="color:Black;background-color:White
<pre> msvcr90.dll!78591641()<br/>
[Frames below may be incorrect and/or missing, no symbols loaded <span style="color:Blue for
msvcr90.dll]
msvcr90.dll!7858cc1b()
kernel32.dll!7c80e14f()
mfc90.dll!78634635()
msvcr90.dll!78583c3a()
msvcr90.dll!785569ed()
msvcr90.dll!785421e7()
ntdll.dll!7c90d80a()
ntdll.dll!7c913416()
msvcr90.dll!785435eb()
msvcr90.dll!78542e2b()
> MaterialManager.dll!_onexit(<span style="color:Blue int
(<span style="color:Blue void
)* func=0x02ecd500) Line 117 + 0x7 bytes C
ntdll.dll!7c90d80a()
kernel32.dll!7c844a01()
kernel32.dll!7c844a14()
mfc90.dll!7865742e()
[/code]

<br/> <br/> <br/> The line in MaterialManager.dll that has an issue is in a file shipped with visual studio (atonexit.c).<br/> The line is crashes at is: 117: "_unlock(_EXIT_LOCK1);"<br/> <br/> I got this by using release with debug info.<br/> <br/> It works completely fine when running a debug build. <br/> <br/> I got this error after trying to remove <br/> #define _HAS_ITERATOR_DEBUGGING 0<br/> and #define _SECURE_SCL 0<br/> from an old code base.<br/> <br/> Thanks.

View the full article
 
Back
Top