NOOP an ASSERT

WINDBG
1

Can someone tell me how to NO-OP an ASSERT (int 3)? What’s the op code for
noop?

Thanks

2

> Can someone tell me how to NO-OP an ASSERT (int 3)? What’s

the op code for noop?

If using SoftICE, use the ZAP cmd

3

Hi!

000:0> a eip
Input> nop
Input>
000:0>

Or use an “eb eip 90”, if you are on an x86.

Cheers,
Felix.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Greg Pearce
Sent: Friday, 22 October 2004 05:45
To: Kernel Debugging Interest List
Subject: [windbg] NOOP an ASSERT

Can someone tell me how to NO-OP an ASSERT (int 3)? What’s the op code
for
noop?

Thanks

You are currently subscribed to windbg as: xxxxx@mvps.org
To unsubscribe send a blank email to xxxxx@lists.osr.com

4

I guess the question is why you want to do this with the debugger, versus
just choosing ignore which will cause the assert not to fire again? If you
were talking about patching it in the binary that is one thing (though a
very bad idea), but why hack something that the system provides a way to
turn off?

–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply

“Greg Pearce” wrote in message news:xxxxx@windbg…
> Can someone tell me how to NO-OP an ASSERT (int 3)? What’s the op code
for
> noop?
>
> Thanks
>
>
>

5

Thanks for the reply - I’m using WinDbg tho. Still learning it after all
these years.

Greg

“Vossen, Joseph (ISS Atlanta)” wrote in message
news:xxxxx@windbg…
> Can someone tell me how to NO-OP an ASSERT (int 3)? What’s
> the op code for noop?

If using SoftICE, use the ZAP cmd

6

Don,
I’m getting the following when running IE, and responding "G"o to it. How
can I make it ignore it?

MSHTML: Assertion Failure in file
D:\nt\private\inet\mshtml\src\site\layout\layout.cxx, line 1646:
MSHTML: pci->_grfLayout & (LAYOUT_MEASURE | LAYOUT_POSITION |
LAYOUT_ADORNERS)
Break instruction exception - code 80000003 (first chance)
mshtml!CLayout::ProcessRequest+0x70:
001b:752dd620 cc int 3
kd> g

Thanks,
Greg

Don Burn" wrote in message news:xxxxx@windbg…

> I guess the question is why you want to do this with the debugger, versus
> just choosing ignore which will cause the assert not to fire again? If
you
> were talking about patching it in the binary that is one thing (though a
> very bad idea), but why hack something that the system provides a way to
> turn off?
>
>
> –
> Don Burn (MVP, Windows DDK)
> Windows 2k/XP/2k3 Filesystem and Driver Consulting
> Remove StopSpam from the email to reply
>
> “Greg Pearce” wrote in message news:xxxxx@windbg…
> > Can someone tell me how to NO-OP an ASSERT (int 3)? What’s the op code
> for
> > noop?
> >
> > Thanks
> >
> >
> >
>
>
>

7

Ok, ignore my comment the kernel assertions have the ability to be ignored.
Of course the real question here is what is the ASSERT complaining about,
and is there a fix?

–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply

“Greg Pearce” wrote in message news:xxxxx@windbg…
> Don,
> I’m getting the following when running IE, and responding “G"o to it. How
> can I make it ignore it?
>
> MSHTML: Assertion Failure in file
> D:\nt\private\inet\mshtml\src\site\layout\layout.cxx, line 1646:
> MSHTML: pci->_grfLayout & (LAYOUT_MEASURE | LAYOUT_POSITION |
> LAYOUT_ADORNERS)
> Break instruction exception - code 80000003 (first chance)
> mshtml!CLayout::ProcessRequest+0x70:
> 001b:752dd620 cc int 3
> kd> g
>
> Thanks,
> Greg
>
> Don Burn” wrote in message news:xxxxx@windbg…
>
> > I guess the question is why you want to do this with the debugger,
versus
> > just choosing ignore which will cause the assert not to fire again? If
> you
> > were talking about patching it in the binary that is one thing (though a
> > very bad idea), but why hack something that the system provides a way to
> > turn off?
> >
> >
> > –
> > Don Burn (MVP, Windows DDK)
> > Windows 2k/XP/2k3 Filesystem and Driver Consulting
> > Remove StopSpam from the email to reply
> >
> > “Greg Pearce” wrote in message news:xxxxx@windbg…
> > > Can someone tell me how to NO-OP an ASSERT (int 3)? What’s the op
code
> > for
> > > noop?
> > >
> > > Thanks
> > >
> > >
> > >
> >
> >
> >
>
>
>

8

Yes, I suppose that’s the “real” question… but I’ve wanted to do this
previously and didn’t know how to do it. I know IBM Assembler but not
Intel. Time to get a book!

Thanks

Greg

“Don Burn” wrote in message news:xxxxx@windbg…
> Ok, ignore my comment the kernel assertions have the ability to be
ignored.
> Of course the real question here is what is the ASSERT complaining about,
> and is there a fix?
>
>
> –
> Don Burn (MVP, Windows DDK)
> Windows 2k/XP/2k3 Filesystem and Driver Consulting
> Remove StopSpam from the email to reply
>
> “Greg Pearce” wrote in message news:xxxxx@windbg…
> > Don,
> > I’m getting the following when running IE, and responding “G"o to it.
How
> > can I make it ignore it?
> >
> > MSHTML: Assertion Failure in file
> > D:\nt\private\inet\mshtml\src\site\layout\layout.cxx, line 1646:
> > MSHTML: pci->_grfLayout & (LAYOUT_MEASURE | LAYOUT_POSITION |
> > LAYOUT_ADORNERS)
> > Break instruction exception - code 80000003 (first chance)
> > mshtml!CLayout::ProcessRequest+0x70:
> > 001b:752dd620 cc int 3
> > kd> g
> >
> > Thanks,
> > Greg
> >
> > Don Burn” wrote in message news:xxxxx@windbg…
> >
> > > I guess the question is why you want to do this with the debugger,
> versus
> > > just choosing ignore which will cause the assert not to fire again?
If
> > you
> > > were talking about patching it in the binary that is one thing (though
a
> > > very bad idea), but why hack something that the system provides a way
to
> > > turn off?
> > >
> > >
> > > –
> > > Don Burn (MVP, Windows DDK)
> > > Windows 2k/XP/2k3 Filesystem and Driver Consulting
> > > Remove StopSpam from the email to reply
> > >
> > > “Greg Pearce” wrote in message news:xxxxx@windbg…
> > > > Can someone tell me how to NO-OP an ASSERT (int 3)? What’s the op
> code
> > > for
> > > > noop?
> > > >
> > > > Thanks
> > > >
> > > >
> > > >
> > >
> > >
> > >
> >
> >
> >
>
>
>

9

The opcode for NOP is 90.

-----Original Message-----
From: Greg Pearce [mailto:xxxxx@filetek.com]
Sent: Friday, October 22, 2004 9:46 AM
To: Kernel Debugging Interest List
Subject: Re:[windbg] NOOP an ASSERT

Yes, I suppose that’s the “real” question… but I’ve wanted to do this
previously and didn’t know how to do it. I know IBM Assembler but not
Intel. Time to get a book!

Thanks

Greg

“Don Burn” wrote in message news:xxxxx@windbg…
> Ok, ignore my comment the kernel assertions have the ability to be
ignored.
> Of course the real question here is what is the ASSERT complaining about,
> and is there a fix?
>
>
> –
> Don Burn (MVP, Windows DDK)
> Windows 2k/XP/2k3 Filesystem and Driver Consulting
> Remove StopSpam from the email to reply
>
> “Greg Pearce” wrote in message news:xxxxx@windbg…
> > Don,
> > I’m getting the following when running IE, and responding “G"o to it.
How
> > can I make it ignore it?
> >
> > MSHTML: Assertion Failure in file
> > D:\nt\private\inet\mshtml\src\site\layout\layout.cxx, line 1646:
> > MSHTML: pci->_grfLayout & (LAYOUT_MEASURE | LAYOUT_POSITION |
> > LAYOUT_ADORNERS)
> > Break instruction exception - code 80000003 (first chance)
> > mshtml!CLayout::ProcessRequest+0x70:
> > 001b:752dd620 cc int 3
> > kd> g
> >
> > Thanks,
> > Greg
> >
> > Don Burn” wrote in message news:xxxxx@windbg…
> >
> > > I guess the question is why you want to do this with the debugger,
> versus
> > > just choosing ignore which will cause the assert not to fire again?
If
> > you
> > > were talking about patching it in the binary that is one thing (though
a
> > > very bad idea), but why hack something that the system provides a way
to
> > > turn off?
> > >
> > >
> > > –
> > > Don Burn (MVP, Windows DDK)
> > > Windows 2k/XP/2k3 Filesystem and Driver Consulting
> > > Remove StopSpam from the email to reply
> > >
> > > “Greg Pearce” wrote in message news:xxxxx@windbg…
> > > > Can someone tell me how to NO-OP an ASSERT (int 3)? What’s the op
> code
> > > for
> > > > noop?
> > > >
> > > > Thanks
> > > >
> > > >
> > > >
> > >
> > >
> > >
> >
> >
> >
>
>
>

—
You are currently subscribed to windbg as: xxxxx@stratus.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

10

Both Intel and AMD will send you copies of the reference manuals for
their current processor families - and amazingly enough, they don’t
charge for it. In addition, I know you can download PDF versions from
the Intel website (finding it can take a few minutes).

Also, Sandpile is an excellent reference source for processor
information (www.sandpile.org) and I generally point people in that
direction…

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Greg Pearce
Sent: Friday, October 22, 2004 9:46 AM
To: Kernel Debugging Interest List
Subject: Re:[windbg] NOOP an ASSERT

Yes, I suppose that’s the “real” question… but I’ve wanted to do this
previously and didn’t know how to do it. I know IBM Assembler but not
Intel. Time to get a book!

Thanks

Greg

“Don Burn” wrote in message news:xxxxx@windbg…
> Ok, ignore my comment the kernel assertions have the ability to be
ignored.
> Of course the real question here is what is the ASSERT complaining
about,
> and is there a fix?
>
>
> –
> Don Burn (MVP, Windows DDK)
> Windows 2k/XP/2k3 Filesystem and Driver Consulting
> Remove StopSpam from the email to reply
>
> “Greg Pearce” wrote in message news:xxxxx@windbg…
> > Don,
> > I’m getting the following when running IE, and responding “G"o to
it.
How
> > can I make it ignore it?
> >
> > MSHTML: Assertion Failure in file
> > D:\nt\private\inet\mshtml\src\site\layout\layout.cxx, line 1646:
> > MSHTML: pci->_grfLayout & (LAYOUT_MEASURE | LAYOUT_POSITION |
> > LAYOUT_ADORNERS)
> > Break instruction exception - code 80000003 (first chance)
> > mshtml!CLayout::ProcessRequest+0x70:
> > 001b:752dd620 cc int 3
> > kd> g
> >
> > Thanks,
> > Greg
> >
> > Don Burn” wrote in message news:xxxxx@windbg…
> >
> > > I guess the question is why you want to do this with the debugger,
> versus
> > > just choosing ignore which will cause the assert not to fire
again?
If
> > you
> > > were talking about patching it in the binary that is one thing
(though
a
> > > very bad idea), but why hack something that the system provides a
way
to
> > > turn off?
> > >
> > >
> > > –
> > > Don Burn (MVP, Windows DDK)
> > > Windows 2k/XP/2k3 Filesystem and Driver Consulting
> > > Remove StopSpam from the email to reply
> > >
> > > “Greg Pearce” wrote in message
news:xxxxx@windbg…
> > > > Can someone tell me how to NO-OP an ASSERT (int 3)? What’s the
op
> code
> > > for
> > > > noop?
> > > >
> > > > Thanks
> > > >
> > > >
> > > >
> > >
> > >
> > >
> >
> >
> >
>
>
>

—
You are currently subscribed to windbg as: xxxxx@osr.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

11

MaryBeth -

That did it!

I was looking at the doc for the wrong Intel assembler. I found the right
thing finally. It’s too early in the morning for me.

Thanks

Greg

12

Excellent! Thanks for the tip Tony…

Greg

“Tony Mason” wrote in message news:xxxxx@windbg…
Both Intel and AMD will send you copies of the reference manuals for
their current processor families - and amazingly enough, they don’t
charge for it. In addition, I know you can download PDF versions from
the Intel website (finding it can take a few minutes).

Also, Sandpile is an excellent reference source for processor
information (www.sandpile.org) and I generally point people in that
direction…

Regards,

Tony

Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Greg Pearce
Sent: Friday, October 22, 2004 9:46 AM
To: Kernel Debugging Interest List
Subject: Re:[windbg] NOOP an ASSERT

Yes, I suppose that’s the “real” question… but I’ve wanted to do this
previously and didn’t know how to do it. I know IBM Assembler but not
Intel. Time to get a book!

Thanks

Greg

“Don Burn” wrote in message news:xxxxx@windbg…
> Ok, ignore my comment the kernel assertions have the ability to be
ignored.
> Of course the real question here is what is the ASSERT complaining
about,
> and is there a fix?
>
>
> –
> Don Burn (MVP, Windows DDK)
> Windows 2k/XP/2k3 Filesystem and Driver Consulting
> Remove StopSpam from the email to reply
>
> “Greg Pearce” wrote in message news:xxxxx@windbg…
> > Don,
> > I’m getting the following when running IE, and responding “G"o to
it.
How
> > can I make it ignore it?
> >
> > MSHTML: Assertion Failure in file
> > D:\nt\private\inet\mshtml\src\site\layout\layout.cxx, line 1646:
> > MSHTML: pci->_grfLayout & (LAYOUT_MEASURE | LAYOUT_POSITION |
> > LAYOUT_ADORNERS)
> > Break instruction exception - code 80000003 (first chance)
> > mshtml!CLayout::ProcessRequest+0x70:
> > 001b:752dd620 cc int 3
> > kd> g
> >
> > Thanks,
> > Greg
> >
> > Don Burn” wrote in message news:xxxxx@windbg…
> >
> > > I guess the question is why you want to do this with the debugger,
> versus
> > > just choosing ignore which will cause the assert not to fire
again?
If
> > you
> > > were talking about patching it in the binary that is one thing
(though
a
> > > very bad idea), but why hack something that the system provides a
way
to
> > > turn off?
> > >
> > >
> > > –
> > > Don Burn (MVP, Windows DDK)
> > > Windows 2k/XP/2k3 Filesystem and Driver Consulting
> > > Remove StopSpam from the email to reply
> > >
> > > “Greg Pearce” wrote in message
news:xxxxx@windbg…
> > > > Can someone tell me how to NO-OP an ASSERT (int 3)? What’s the
op
> code
> > > for
> > > > noop?
> > > >
> > > > Thanks
> > > >
> > > >
> > > >
> > >
> > >
> > >
> >
> >
> >
>
>
>

—
You are currently subscribed to windbg as: xxxxx@osr.com
To unsubscribe send a blank email to xxxxx@lists.osr.com