Debugging

[Guest]

Archived from groups: microsoft.public.win2000.security (More info?)

Computer locks up and when you try to end program you get
this message: "This program cannot be closed. If if is
being debugged, please resume it or close the debugger
first."
We are unaware of any debugger running.

 

[Dave]

Archived from groups: microsoft.public.win2000.security (More info?)

i think it reports that when dr.watson is making its dump, that uses some of
the same api's as debuggers do to access the memory space of the crashed
app.

<smacrae@mpbcpa.com> wrote in message
news:0a0901c4a24c$7325d550$a501280a@phx.gbl...
> Computer locks up and when you try to end program you get
> this message: "This program cannot be closed. If if is
> being debugged, please resume it or close the debugger
> first."
> We are unaware of any debugger running.

 

[Guest]

Archived from groups: microsoft.public.win2000.security (More info?)

To add to that it might help looking to see if anything was reported in Event Viewer.
You can try to disable debug logging if you do not need it in System
Properties/advanced/startup and recovery/write debugging information - none. ---
Steve


"Dave" <noone@nowhere.com> wrote in message
news:efewaMloEHA.2764@TK2MSFTNGP11.phx.gbl...
>i think it reports that when dr.watson is making its dump, that uses some of
> the same api's as debuggers do to access the memory space of the crashed
> app.
>
> <smacrae@mpbcpa.com> wrote in message
> news:0a0901c4a24c$7325d550$a501280a@phx.gbl...
>> Computer locks up and when you try to end program you get
>> this message: "This program cannot be closed. If if is
>> being debugged, please resume it or close the debugger
>> first."
>> We are unaware of any debugger running.
>
>