New
#1
General Comments
Thank you for the detailed explanation.
H2SO4
thanks for a great intro to debugging
Hello H2SO4.
It would be best if the other posts were removed from this and the thread locked so that it won't get filled up with extraneous posts like this one, that way the info won't be hard to find in all the extra posts.
Which software ?
Missed one:
Even More Debugger Trickery For The Really InterestedMinidumps can also easily reveal basic information about the Windows version, service pack level, time of the crash, and system uptime:1: kd> vertarget
Windows Server 2008/Windows Vista Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x64
Bare Foot Kid said:Thanks guys. I don't mind what the moderators and admins choose to do with it, though in some ways I'd rather keep it here rather than see it go to "tutorials". It may be more visible to those who come to this section because they've got a problem, rather than because they're looking for a tutorial on debugging.Tews said:
As far as extraneous posts (like this one) and locking are concerned, I imagine that would have to be handled by a moderator? It would be nice if the thread could remain at least partially interactive, so that questions could be asked (and maybe even answered), and others may contribute. Perhaps the non-core posts could simply be culled every so often?
Roger that!
Its just that being w7, noobs might have difficulty following,
and become confused with dinosaur terminology.
Nobody's gonna check 'symbol references',
APIs in .h, or anything like that...
I see your point. Done. I have angered the gods of debugging by editing that first post to show Win7 as the name of the OS being debugged.
To punish me, some 7th-Dan Pedant is now going to come out of the woodwork to point out that the information is inconsistent because the modules list doesn't match the preferred load addresses for Win 7