Re: Crashes in Debug (random) but not release
- From: "Chris Scott" <donotATmailDOTcom>
- Date: Wed, 13 Apr 2005 15:21:59 -0400
It's sounds like memory corruption of some kind. I've tracked things like
this before and seen some really strange things that would fix it like:
Swapping the order of global variables.
Reducing the overall memory footprint of the application (loading too much
data or more than is absolutely necessary)
Increasing the overall memory footprint of the application =)
I'd only try those above after you've triple checked the following:
Writing beyond array boundaries
Using uninitialized pointers
Failing to clean up resources
.
- Follow-Ups:
- Re: Crashes in Debug (random) but not release
- From: Timothy Dean
- Re: Crashes in Debug (random) but not release
- References:
- Crashes in Debug (random) but not release
- From: Timothy Dean
- Re: Crashes in Debug (random) but not release
- From: r_z_aret
- Re: Crashes in Debug (random) but not release
- From: Timothy Dean
- Crashes in Debug (random) but not release
- Prev by Date: Re: Look up currently running programs?
- Next by Date: Re: RAD tool for Pocket PC
- Previous by thread: Re: Crashes in Debug (random) but not release
- Next by thread: Re: Crashes in Debug (random) but not release
- Index(es):
Relevant Pages
|