corrupt callstack after crash in release
-
Hi, I've been working on this one for some days now and I'm all out of ideas. My program works just fine when it is build for debug, but when I build it for release it crashes at some point. Now, when I tried to analyze the crash dump information, I saw that the callstack got corrupt so I can't do anything with it. I've tried using BoundsChecker on both the release and debug exe but it doesn't report anything (except for the access violation of course...) My next idea was to add some logging (to a file) in my program so I could trace where exactly I was going in my code. The problem now is that by adding code for logging purposes I'm changing the stack of my program so that again it doesn't crash anymore. I have been able to make up in which function the crash occurs, but placing logging inside that function "prevents" the crash... I hope there is someone out there who has run into a similar problem and was able to solve it. Any ideas are welcome greetz Don't think you are, know you are...
-
Hi, I've been working on this one for some days now and I'm all out of ideas. My program works just fine when it is build for debug, but when I build it for release it crashes at some point. Now, when I tried to analyze the crash dump information, I saw that the callstack got corrupt so I can't do anything with it. I've tried using BoundsChecker on both the release and debug exe but it doesn't report anything (except for the access violation of course...) My next idea was to add some logging (to a file) in my program so I could trace where exactly I was going in my code. The problem now is that by adding code for logging purposes I'm changing the stack of my program so that again it doesn't crash anymore. I have been able to make up in which function the crash occurs, but placing logging inside that function "prevents" the crash... I hope there is someone out there who has run into a similar problem and was able to solve it. Any ideas are welcome greetz Don't think you are, know you are...
If you spotted the offending function, then you're nearly at it. Try posting the code here, maybe someone can see the error. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo
-
Hi, I've been working on this one for some days now and I'm all out of ideas. My program works just fine when it is build for debug, but when I build it for release it crashes at some point. Now, when I tried to analyze the crash dump information, I saw that the callstack got corrupt so I can't do anything with it. I've tried using BoundsChecker on both the release and debug exe but it doesn't report anything (except for the access violation of course...) My next idea was to add some logging (to a file) in my program so I could trace where exactly I was going in my code. The problem now is that by adding code for logging purposes I'm changing the stack of my program so that again it doesn't crash anymore. I have been able to make up in which function the crash occurs, but placing logging inside that function "prevents" the crash... I hope there is someone out there who has run into a similar problem and was able to solve it. Any ideas are welcome greetz Don't think you are, know you are...
You are probably trashing a stack array. Maybe a character string or some such thing. You might also be returning a pointer to a stack variable. This can cause all sorts of strange problems. Tim Smith I'm going to patent thought. I have yet to see any prior art.
-
Hi, I've been working on this one for some days now and I'm all out of ideas. My program works just fine when it is build for debug, but when I build it for release it crashes at some point. Now, when I tried to analyze the crash dump information, I saw that the callstack got corrupt so I can't do anything with it. I've tried using BoundsChecker on both the release and debug exe but it doesn't report anything (except for the access violation of course...) My next idea was to add some logging (to a file) in my program so I could trace where exactly I was going in my code. The problem now is that by adding code for logging purposes I'm changing the stack of my program so that again it doesn't crash anymore. I have been able to make up in which function the crash occurs, but placing logging inside that function "prevents" the crash... I hope there is someone out there who has run into a similar problem and was able to solve it. Any ideas are welcome greetz Don't think you are, know you are...
The first thing to check is that all you modules use same CRT model (lets say /MDd) "Project settings->C/C++->Code Generation->Runtime Library" page. The second is to debug. When stack gets corrupted it is easy to see in debug right the way (assuming you know the approximate location.
-
Hi, I've been working on this one for some days now and I'm all out of ideas. My program works just fine when it is build for debug, but when I build it for release it crashes at some point. Now, when I tried to analyze the crash dump information, I saw that the callstack got corrupt so I can't do anything with it. I've tried using BoundsChecker on both the release and debug exe but it doesn't report anything (except for the access violation of course...) My next idea was to add some logging (to a file) in my program so I could trace where exactly I was going in my code. The problem now is that by adding code for logging purposes I'm changing the stack of my program so that again it doesn't crash anymore. I have been able to make up in which function the crash occurs, but placing logging inside that function "prevents" the crash... I hope there is someone out there who has run into a similar problem and was able to solve it. Any ideas are welcome greetz Don't think you are, know you are...
This article may help. http://www.codeproject.com/debug/survivereleasever.asp[^] Also the BugSlayer column by John Robbins on MSDN/MSJ and his book, and the WheetyExceptionReport code by Matt Pietrek (spelling) also on MSDN. Neville Franks, Author of ED for Windows. www.getsoft.com Make money with our new Affilate program