You can get Public symbols for most builds via http from Microsoft. These contain enough information to get you a stack trace but not local variables or source code file/line index information. Consult the Debugging Tools for Windows documentation if you want the nitty-gritty details.
If only. You need to download the debugging symbols to make any sense of BSOD crash reports. That's always fun trying to find out why a new machine is crashing. First step: Download several hundred MB for your build Step two: Install a few programs that really should be part of the windows installation in the first place. Step three: Follow some online guides and realise that your BSOD is nearly always caused by some dll with Mcafee in the publisher name.
Heard that the next Space Shuttle is supposed to carry several Guernsey cows?
It's gonna be the herd shot 'round the world.
Debug Symbols? (Score:5, Interesting)
Did the builds have debug symbols? That would be a goldmine for reverse-engineers.
Re: (Score:3, Informative)
You can get Public symbols for most builds via http from Microsoft. These contain enough information to get you a stack trace but not local variables or source code file/line index information. Consult the Debugging Tools for Windows documentation if you want the nitty-gritty details.
Re: (Score:2)
If only. You need to download the debugging symbols to make any sense of BSOD crash reports. That's always fun trying to find out why a new machine is crashing. First step: Download several hundred MB for your build
Step two: Install a few programs that really should be part of the windows installation in the first place.
Step three: Follow some online guides and realise that your BSOD is nearly always caused by some dll with Mcafee in the publisher name.