Re: Need Help Debugging
- From: Johannes Passing <jpassing_at_hotmail_com@xxxxxxxxxx>
- Date: Mon, 24 Sep 2007 20:41:06 +0200
What is the code of the exception that brings your application down? You can look it up under 'Exception number' in the DrWatson Log. The code should give you a hint on the reason of the crash.
--Johannes
Ben wrote:
I have a non-managed c++ service that has a crash periodically.
I analyze the DrWatson dump and every time it seems to point to a
ntdll!RtlInitializeCriticalSectionAndSpinCount. I do use
CRITICAL_SECTIONS often throughout the code to manage access to the
variables, since it's a multi-threaded app.
Is there a certain rule of thumb when using Critical Sections to avoid
this ? I saw in MSDN they say to call
InitializeCriticalSectionAndSpinCount instead of just
InitializeCriticalSection in order to avoid memory resource exceptions
on pre-windows-XP systems... but our clients are XP, so I think i'm ok
with using InitializeCriticalSection. Maybe there's something more
recommended to use ?
In my searches, i'm seen some references to stack overflows... i'm not
too familiar with how to avoid it ? can someone offer some
guidance ? I know we use some string variables that can hold a few MB
of xml data... usually they are declared as an STL "string" and passed
as references. Do I need to use 'new' to allocate these large vars ?
does that avoid using the stack ?!?
Thanks for any tips!
ben
--
Johannes Passing - http://int3.de/
.
- Follow-Ups:
- Re: Need Help Debugging
- From: Ben
- Re: Need Help Debugging
- References:
- Need Help Debugging
- From: Ben
- Need Help Debugging
- Prev by Date: Re: Obtaining volume path name from open file handle
- Next by Date: Re: Need Help Debugging
- Previous by thread: Re: Need Help Debugging
- Next by thread: Re: Need Help Debugging
- Index(es):
Relevant Pages
|