From: Digital I. Inc. <ok...@di...> - 2004-02-01 21:48:39
|
Hello ePAc. Thank you for reply. Your opinion is useful. Although I dont know if it works for coLinux. How about this idea, Aloni? As I wrote, there would be very many ways to do it. so we have to discuss about many options before we start to develop. Any opinion is welcome. I need your help, everyone. --- Okajima, Jun. President, Digital Infra, Inc. Tokyo, Japan. > >> We apparently have to get some measures to get information about >> what is going on under a blue screen of death. One way is using >> a memory dump. And there must be many ideas, papers, codes to do it. >> To prevent re-inventing the wheel, I ask you to post ideas, >> URLs, papers,,,, about this issue. >> > >how about just using the tools that microsoft is providing us to analyze >the dumps... > >http://www.microsoft.com/whdc/ddk/debugging/installx86.mspx > >the "dumpchk.exe" tool will generate a backtrace of what generated the >BSOD (unless it can't with something like memory corruption). > >given the proper symbols, you can get a pretty detailed backtrace of the >crash. > >i'll be producing the debug info from the dump file i have shortly... > >Thanks, >Jok > >--- >Nothing is foolproof to a sufficiently talented fool... > oo >,(..)\ > ~~ > |