Re: How to debug "new operator" crash ?
I highly recommend OP invests in a memory tracking tool like
BoundsChecker, Insure++, or Purify. Despite the high cost, it's
much cheaper in the long run than debugging without one...
--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@mvps.org
MVP VC FAQ: http://vcfaq.mvps.org
=====================================
"Tim Roberts" <timr@probo.com> wrote in message
news:t3oem3ho1d3u9plv2q3uo1cs68rhd8ksfk@4ax.com...
acolor0429@gmail.com wrote:
My program is a multithread application, the problem is it
occasionally gets crashed when using "new operator". I check other
threads, they are all stopped at "new operator". All those threads
seem to get the same problem. Can anyone tell me why or teach me how
to debug this case?
Here is the call stacks:
[The crashed thread]:
00 ntdll!KiFastSystemCallRet
01 ntdll!ZwWaitForMultipleObjects+0xc
02 kernel32!WaitForMultipleObjectsEx+0x12c
03 kernal32!WaitForMultipleObjects+0x18
04 faultrep!StartDWException+0x5df
05 faultrep!ReportFault+0x533
06 kernel32!UnhandledExceptionFilter+0x587
07 msvcrt!_XcptFilter+0x161
08 msvcrt!_endthreadex+0xc0
09 msvcrt!_except_handler3+0x61
0a ntdll!ExecuteHandler2+0x26
0b ntdll!ExecuteHandler+0x24
0c ntdll!KiUserExceptionDispatcher+0xe
0d ntdll!RtlAllocateHeap+0x917
0e msvcrt!_heap_alloc+0xe0
0f msvcrt!_nh_malloc+0x13
10 msvcrt!operator new+0xf
11 (My AP)!ClassA::ClassA <= constructor
12 (My AP)
Looks pretty clear to me. This thread did a "new" to try allocate a new
object, and RtlAllocateHeap threw an exception. You probably have this
caught in a debugger, while holding the heap's interlock, and that
prevents
any other threads from continuing.
So, you need to figure out why RtlAllocateHeap threw an exception. The
two
primary guesses would be either you have trashed the heap, by writing
beyond the end of a buffer, or you have run out of memory.
--
Tim Roberts, timr@probo.com
Providenza & Boekelheide, Inc.