Silent Crash On 2K - Debug Suggestions?
-
VC++ 6, MFC, SP5, WinXP - Home :~ . I've spent the last few months writing an application for work (They found out I do some programming for fun and now it's part of my job :~ ) Anyway, The application is done and runs fine on XP. Both the release version and debug version run well, debug shows no memory leaks or asserts (other then the asserts I want it to show.) So anyway, I try to run it on Win 2K and the app crashes at start up. No chance for the main window to open or anything. The crash is not a GPF or a blue screen, just a small message box that states "Your program has done something I don't like and will close now. A log is being created. OK." - Well, that's not the actual message but the jest of it ...and it doesn't tell me where the darn log is!!! :mad: I know I took a lot of care to use API functions that would work all the way down to Win 95, so I'm kind of stummped. I even used some of the debugging code here on Codeproject to insert into the application during debug builds and it shows everything was A-OK. Anyone have any ideas of where I can even start looking for the cause of this crash? Thanks for any advice. -- modified at 23:00 Tuesday 6th September, 2005
-
VC++ 6, MFC, SP5, WinXP - Home :~ . I've spent the last few months writing an application for work (They found out I do some programming for fun and now it's part of my job :~ ) Anyway, The application is done and runs fine on XP. Both the release version and debug version run well, debug shows no memory leaks or asserts (other then the asserts I want it to show.) So anyway, I try to run it on Win 2K and the app crashes at start up. No chance for the main window to open or anything. The crash is not a GPF or a blue screen, just a small message box that states "Your program has done something I don't like and will close now. A log is being created. OK." - Well, that's not the actual message but the jest of it ...and it doesn't tell me where the darn log is!!! :mad: I know I took a lot of care to use API functions that would work all the way down to Win 95, so I'm kind of stummped. I even used some of the debugging code here on Codeproject to insert into the application during debug builds and it shows everything was A-OK. Anyone have any ideas of where I can even start looking for the cause of this crash? Thanks for any advice. -- modified at 23:00 Tuesday 6th September, 2005
-- modified at 23:42 Tuesday 6th September, 2005 For the record, I deleted this because CP posted it twice....
-
VC++ 6, MFC, SP5, WinXP - Home :~ . I've spent the last few months writing an application for work (They found out I do some programming for fun and now it's part of my job :~ ) Anyway, The application is done and runs fine on XP. Both the release version and debug version run well, debug shows no memory leaks or asserts (other then the asserts I want it to show.) So anyway, I try to run it on Win 2K and the app crashes at start up. No chance for the main window to open or anything. The crash is not a GPF or a blue screen, just a small message box that states "Your program has done something I don't like and will close now. A log is being created. OK." - Well, that's not the actual message but the jest of it ...and it doesn't tell me where the darn log is!!! :mad: I know I took a lot of care to use API functions that would work all the way down to Win 95, so I'm kind of stummped. I even used some of the debugging code here on Codeproject to insert into the application during debug builds and it shows everything was A-OK. Anyone have any ideas of where I can even start looking for the cause of this crash? Thanks for any advice. -- modified at 23:00 Tuesday 6th September, 2005
If a log was created, it's probably in the system event log. My first step with problems like this is to create a global file object, and to use it to log how far the app gets before crashing, and work out what line is blowing up through a process of elimination. Christian Graus - Microsoft MVP - C++
-
If a log was created, it's probably in the system event log. My first step with problems like this is to create a global file object, and to use it to log how far the app gets before crashing, and work out what line is blowing up through a process of elimination. Christian Graus - Microsoft MVP - C++
Thanks for the idea! ;) Sort of like a debug output screen but written to a file. That it too simple! :-O And off the record, your other message was deleted because you were really listening to Iron Maiden again, right? :-D Thanks for the help! Paul...
-
Thanks for the idea! ;) Sort of like a debug output screen but written to a file. That it too simple! :-O And off the record, your other message was deleted because you were really listening to Iron Maiden again, right? :-D Thanks for the help! Paul...
Nah, I just got the Hollywood Rocks box set, so I have no idea who I'm listening to from one moment to the next, but it's all good... Christian Graus - Microsoft MVP - C++
-
VC++ 6, MFC, SP5, WinXP - Home :~ . I've spent the last few months writing an application for work (They found out I do some programming for fun and now it's part of my job :~ ) Anyway, The application is done and runs fine on XP. Both the release version and debug version run well, debug shows no memory leaks or asserts (other then the asserts I want it to show.) So anyway, I try to run it on Win 2K and the app crashes at start up. No chance for the main window to open or anything. The crash is not a GPF or a blue screen, just a small message box that states "Your program has done something I don't like and will close now. A log is being created. OK." - Well, that's not the actual message but the jest of it ...and it doesn't tell me where the darn log is!!! :mad: I know I took a lot of care to use API functions that would work all the way down to Win 95, so I'm kind of stummped. I even used some of the debugging code here on Codeproject to insert into the application during debug builds and it shows everything was A-OK. Anyone have any ideas of where I can even start looking for the cause of this crash? Thanks for any advice. -- modified at 23:00 Tuesday 6th September, 2005
If you can get your program 'started' then you should download the "Debugging Tools for Windows" form Microsoft's website. Install it. Read about running 'AdPlus to capture the 'crash' mode. Then look at the DMP file using WinDBG (have all the PDB files for your project handy) and you can probably determine exactly where and why your program crashes.