Comments for Analyze -v

Comment on Break on user mode module load by Tweets that mention Break on user mode module load « Analyze -v -- Topsy.com

Tweets that mention Break on user mode module load « Analyze -v -- Topsy.com — Sat, 21 Aug 2010 01:04:45 +0000

[...] This post was mentioned on Twitter by 0vercl0k, `Ivan. `Ivan said: Break on user mode module load http://bit.ly/bhW0jv [...]

Comment on Break on user mode module load by NCR

NCR — Fri, 20 Aug 2010 23:53:17 +0000

Nice!. Thanks for sharing!.

Comment on Process specific breakpoints by Break on user mode module load « Analyze -v

Break on user mode module load « Analyze -v — Fri, 20 Aug 2010 21:51:55 +0000

[...] need to have the debugger break in when a user mode module loads. For example, I may want to set a process specific breakpoint but the process in question isn’t loaded yet. Normally this would be a giant pain, but with a [...]

Comment on Associate WinDBG With .DMP Files by Quickly add the dump path to your symbol path « Analyze -v

Quickly add the dump path to your symbol path « Analyze -v — Tue, 17 Aug 2010 23:37:24 +0000

[...] the appropriate PDBs for the images in the dump. I then have to extract the dump file to a folder, double click on the DMP file, and then add the path to the unzipped dump to my symbol search path so that I grab the appropriate [...]

Comment on Dog days of Summer by Marc Sherman

Marc Sherman — Fri, 23 Jul 2010 21:46:10 +0000

Looking forward to both your blog posts and more NT Insider. Enjoy the rest of your vacation!

Comment on What are the “Args to Child” in the kv output? by snoone

snoone — Tue, 22 Jun 2010 16:26:26 +0000

Glad it helped!

Comment on What are the “Args to Child” in the kv output? by Jason Mobarak

Jason Mobarak — Tue, 22 Jun 2010 14:45:41 +0000

Thanks for the concise explanation!

Comment on Thread specific breakpoints by Process specific breakpoints « Analyze -v

Process specific breakpoints « Analyze -v — Fri, 21 May 2010 03:46:30 +0000

[...] talked previously about thread specific breakpoints, which allow you to set a breakpoint that will only fire for a specific thread. Equally useful are [...]

Comment on Driver Speak: IRQL by David Moisan

David Moisan — Thu, 13 May 2010 00:01:35 +0000

The old timesharing minicomputer I used in high school (late seventies) was a PDP-11/60 with RSTS/E. Emulators and images are still available but that’s off the point. The real point is getting a mimeographed copy of RSTS internals for systems programming.

There was a structure known as a FIRQB. Without looking for my mimeos which are in a box with the rest of my fanfold printouts from that era, it was not an IRQL (which would not be exposed as we understand it today) but more like a control block or perhaps a structure that was passed to the RSTS system dispatch table via the SYS() function. (In BASIC. No joke.)

It is pronounced–and I remember this very clearly–”Furk-be!”

Don’t ask why that triggered my memory.

Comment on Great description of IRQL by Jake Oshins by Driver Speak: IRQL « Analyze -v

Driver Speak: IRQL « Analyze -v — Wed, 12 May 2010 12:14:54 +0000

[...] request levels are a fundamental Windows concept. We all know what they are (and if not we should)