Ch9Live at Tech.Ed NA 2010 - Ask Mark Russinovich Anything... LIVE!

Will system internals tools be released as open source?  I have Mark's latest edition of the system internals book. I would have gotten more out of the book if it showed how to get at the sys internals info with your own windows and kernel api code.

Can I halt a running process in Windows and then examine the call stack of each of the threads of the process?

For some reason, sql server gives me all sorts of grief when I do installs, edition upgrades or try to use it from a user account.
http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/00f6560b-31b6-48cb-84b4-0d960f8a199f
http://social.msdn.microsoft.com/Forums/en-US/sqlexpress/thread/5b39146b-cb0e-4617-8e14-f6f6bef5bb85

( on that first case, I am 2 weeks in and MSDN still cannot correct the problem. Not that they are putting much effort into it.  But it is an open case. )

Ideal, I think,would be if every process had a run log associated with it. Apps would have a common, always there, place to write diagnostic and error messages to. Pretty much what the IBM AS400 has with job logs and spooled output files.  In the case of my sql server troubles, when sql server decides it can't do something it would write detailed info about the error to the run log. Windows would store the run logs of completed processes. To review a problem, open up the runlog of the completed process and review the messages.

Cool

More of Mark )

It's called the Event Log.