Selon "Curtis L. Olson" : > MPCEE French Bureau wrote: > > >Hello Curtis: > > > >Windows comes with a debugger. It's an operation in from the IE browser > > >Internet Options > Advanced then you can able or disable bugging > >information. I use it a lot because of the vast number of sites where the > >creators have no idea how to set up script! It will pinpoint the line and > >the error. Is this what you have in mind? > > > > > > Errr, really? I really doubt it, but but please prove me wrong, and > tell us the line and the source file of the error! It would really > help. If you give us something that looks like a screenshot of the blue > screen of death with registry values and physical memory locations of > the crash, that is nearly useless. We need/want to pin point the > location in the original source code of the crash.
I really doubt there is a native code debugger in Windows. I never found one. Martin surely refer to debugging CLR code that is a bytecode more or less MS response to Java. I also doubt it could be useful on the current binary as debugging informations are not there ( not stripped, simply not generated for performance reason ). The only relevant standard tool is DrWatson that only give binary trace and registers. What can be done though, is running the remote debugger provided with Visual Studio. A small exe is run on the target platform. It launch the version of the program that was compiled with debug information, and a developer connect to the target site and run the debugger at its side. If someone with problems is volunteering to play the guinea pig, we can arrange a debugging session. -Fred _______________________________________________ Flightgear-users mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
