Softice question

NTDEV
1

Alberto,
Since I know who are now, can I bend your ear? When trapping faults
with softice, how can I get the fault information to show like it does in
the blue screen (same info, not look same). For example, I was getting a
0xc4 trap with 4 parameters of info that the driver verifier caught. It is
not obvious to me how to see that same info when caught by Softice. What I
would end up doing is turning faults off and let it continue, which didn’t
always give me the BSOD I was after. There is probably some really easy
way to do this, but it has missed me so far. I wish the Numega doc’s
offered more info on actually how to use the debugger (there are exhaustive
amouts of info on how to do things in windbg). I often find that it can do
something I want but I don’t know how to find the info in the docs.

Thanks,
Justin

2

Oops,
With 0xC4 traps it does show the info. It was some other ones it
could not interpret but the XP handler could. Actually, it could be that
Softice has not been updated to interpret some of the newer verifier traps.

-Justin

At 02:25 PM 10/16/2002, you wrote:

Alberto,
Since I know who are now, can I bend your ear? When trapping faults
with softice, how can I get the fault information to show like it does in
the blue screen (same info, not look same). For example, I was getting a
0xc4 trap with 4 parameters of info that the driver verifier caught. It
is not obvious to me how to see that same info when caught by
Softice. What I would end up doing is turning faults off and let it
continue, which didn’t always give me the BSOD I was after. There is
probably some really easy way to do this, but it has missed me so far. I
wish the Numega doc’s offered more info on actually how to use the
debugger (there are exhaustive amouts of info on how to do things in
windbg). I often find that it can do something I want but I don’t know
how to find the info in the docs.

Thanks,
Justin

You are currently subscribed to ntdev as: zeppelin@io.com
To unsubscribe send a blank email to %%email.unsub%%

3

I looked at the source code. In many cases we try to decode the info and
show it on the command window. Sometimes we display more info than that,
sometimes not. I was actually surprised at how many subcases we cover, but
it’s always possible to get one that we don’t. That functionality, AFAIK,
has been there since 2.5 at least, but on the other hand only 2.7 does a
decent job of running under XP.

Alberto.

-----Original Message-----
From: Justin Frodsham [mailto:zeppelin@io.com]
Sent: Thursday, October 17, 2002 12:26 AM
To: NT Developers Interest List
Subject: [ntdev] Re: Softice question

Oops,
With 0xC4 traps it does show the info. It was some other ones it
could not interpret but the XP handler could. Actually, it could be that
Softice has not been updated to interpret some of the newer verifier traps.

-Justin

At 02:25 PM 10/16/2002, you wrote:

Alberto,
Since I know who are now, can I bend your ear? When trapping faults
with softice, how can I get the fault information to show like it does in
the blue screen (same info, not look same). For example, I was getting a
0xc4 trap with 4 parameters of info that the driver verifier caught. It
is not obvious to me how to see that same info when caught by
Softice. What I would end up doing is turning faults off and let it
continue, which didn’t always give me the BSOD I was after. There is
probably some really easy way to do this, but it has missed me so far. I
wish the Numega doc’s offered more info on actually how to use the
debugger (there are exhaustive amouts of info on how to do things in
windbg). I often find that it can do something I want but I don’t know
how to find the info in the docs.

Thanks,
Justin

You are currently subscribed to ntdev as: zeppelin@io.com
To unsubscribe send a blank email to %%email.unsub%%

You are currently subscribed to ntdev as: xxxxx@compuware.com
To unsubscribe send a blank email to %%email.unsub%%

The contents of this e-mail are intended for the named addressee only. It
contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose
it to anyone else. If you received it in error please notify us immediately
and then destroy it.