windbg behavior on assert

Windbg stops on assert. It prints:
*** Assertion failed: bVariable == TRUE
*** Source File: .\Filename.c, line 950

Break repeatedly, break Once, Ignore, terminate Process, or terminate Thread


I read in debugger doc about command ahi:

ahi
Causes the debugger to ignore an assertion failure at the specified address
Address
Specifies the address of the instruction whose assertion-handling status is
being set. If this is omitted, the current program counter is used.

But when I type "ahi" and press enter,
debugger does not restore run, but it again prints the same.

When I try menu View -> Registers (to see eip),
nothing displays in window neither register names.

When I try menu View->Disasembly, it appears:
"User interface suspended, use .suspend_ui 0 to re-enable".

What magic to do with it - to resume execution ?

Peter

To ignore this assertion type "i" and press enter.

Best regards,
Fisyuk Victor
EMail/MSN:
Web: http://rockdbg.siteburg.com

"Peter" <> wrote in message
news:3D935504-6625-476F-866A-...
> Windbg stops on assert. It prints:
> *** Assertion failed: bVariable == TRUE
> *** Source File: .\Filename.c, line 950
>
> Break repeatedly, break Once, Ignore, terminate Process, or terminate
> Thread
>
>
> I read in debugger doc about command ahi:
>
> ahi
> Causes the debugger to ignore an assertion failure at the specified
> address
> Address
> Specifies the address of the instruction whose assertion-handling status
> is
> being set. If this is omitted, the current program counter is used.
>
> But when I type "ahi" and press enter,
> debugger does not restore run, but it again prints the same.
>
> When I try menu View -> Registers (to see eip),
> nothing displays in window neither register names.
>
> When I try menu View->Disasembly, it appears:
> "User interface suspended, use .suspend_ui 0 to re-enable".
>
> What magic to do with it - to resume execution ?
>
> Peter
>
>