Post-mortem debugging under Win7 Home Premium
-
Hello folks! This question isn't strictly C++/MFC related, but i do not know where to ask, so i ask you here. We have a few minidumps created when our software crashed at a betasite. The software is written in VC++/MFC (that's why i thought i ask here, maybe you experienced something like this too). When i try to open the minidumps in VS2003 i get the Blue Screen Of Death. First i thought this would be because 2003 is not supported on Win7. Now we acquired VS2010, but opening the crash dumps in VS2010 also gives me the sky-colored display of decease. Someone suggested that it might be because Home Premium doesn't support this function, but i highly doubt it, since if it was this case i'd expect to: -see at least a warning about it when installing Visual Studio or trying to use dump-related things -some nice window popping up telling me to rather buy the ultimate super-pro megaversion of windows which costs only 6 times the one i have now. Googling for BSOD on crash dump analysis gives me loads of hits about how to analyse crash dumps created when Windows BSODs, none about why Windows might die if you try to analyse crash dumps. (Hey, i could try analysing the crash dump of the BSOD, so i try to open it in VS...oups, BSOD, hey, i could try analysing the crash dump of this BSOD, so i try to open it in VS...oups, BSOD, hey, i could try analysing... just kidding) Any of you heard/ran into anything like this before? Ah, another thing that might or might not be relevant, the dumps come from a 32 bit system while i am running on 64 bit. My colegue has Win7 Pro, also 64 bit, he has no trouble opening the dumps. Thanks in advance for any suggestions, ideas, infoes, and sorry for the somewhat off-topic topic.
> The problem with computers is that they do what you tell them to do and not what you want them to do. < > If it doesn't matter, it's antimatter.<
-
Hello folks! This question isn't strictly C++/MFC related, but i do not know where to ask, so i ask you here. We have a few minidumps created when our software crashed at a betasite. The software is written in VC++/MFC (that's why i thought i ask here, maybe you experienced something like this too). When i try to open the minidumps in VS2003 i get the Blue Screen Of Death. First i thought this would be because 2003 is not supported on Win7. Now we acquired VS2010, but opening the crash dumps in VS2010 also gives me the sky-colored display of decease. Someone suggested that it might be because Home Premium doesn't support this function, but i highly doubt it, since if it was this case i'd expect to: -see at least a warning about it when installing Visual Studio or trying to use dump-related things -some nice window popping up telling me to rather buy the ultimate super-pro megaversion of windows which costs only 6 times the one i have now. Googling for BSOD on crash dump analysis gives me loads of hits about how to analyse crash dumps created when Windows BSODs, none about why Windows might die if you try to analyse crash dumps. (Hey, i could try analysing the crash dump of the BSOD, so i try to open it in VS...oups, BSOD, hey, i could try analysing the crash dump of this BSOD, so i try to open it in VS...oups, BSOD, hey, i could try analysing... just kidding) Any of you heard/ran into anything like this before? Ah, another thing that might or might not be relevant, the dumps come from a 32 bit system while i am running on 64 bit. My colegue has Win7 Pro, also 64 bit, he has no trouble opening the dumps. Thanks in advance for any suggestions, ideas, infoes, and sorry for the somewhat off-topic topic.
> The problem with computers is that they do what you tell them to do and not what you want them to do. < > If it doesn't matter, it's antimatter.<
For crash dumps you need to use Windbg.exe to analyze them. You can get it straight off MSDN website. Its an interesting debugger, very powerful, very very complex. But there is a help file which takes you through various debugging techniques as part of the install, read it and give it a go.
============================== Nothing to say.
-
For crash dumps you need to use Windbg.exe to analyze them. You can get it straight off MSDN website. Its an interesting debugger, very powerful, very very complex. But there is a help file which takes you through various debugging techniques as part of the install, read it and give it a go.
============================== Nothing to say.
I'll give it a spin, thank you.
> The problem with computers is that they do what you tell them to do and not what you want them to do. < > If it doesn't matter, it's antimatter.<