Hi,
So there is a try/except block that has been getting access violation, I hooked up windbg to see where, it trapped it and can see. But I can’t continue on, I’m stuck on the access violation. I went to debug/event filters changed the “access violation” to all different kinds of settings and still won’t continue (output, just keeps outputting the same text), disable still break, enable breaks, ignore just doesn’t do anything have to break and at same location, changing handled/not handled didn’t do anything. How do I get it to continue and trap in my try/except loop as it has been without windbg ?
TIA!!
Second chance exception means no exception handler was able to handle that
exception and the application/kernel can’t continue anymore and will crash.
On Sat, May 13, 2017 at 1:01 AM, wrote:
> Hi,
>
> So there is a try/except block that has been getting access violation, I
> hooked up windbg to see where, it trapped it and can see. But I can’t
> continue on, I’m stuck on the access violation. I went to debug/event
> filters changed the “access violation” to all different kinds of settings
> and still won’t continue (output, just keeps outputting the same text),
> disable still break, enable breaks, ignore just doesn’t do anything have to
> break and at same location, changing handled/not handled didn’t do
> anything. How do I get it to continue and trap in my try/except loop as it
> has been without windbg ?
>
> TIA!!
>
>
> —
> WINDBG is sponsored by OSR
>
> OSR is hiring!! Info at http://www.osr.com/careers
>
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
> software drivers!
> Details at http:
>
> To unsubscribe, visit the List Server section of OSR Online at <
> http://www.osronline.com/page.cfm?name=ListServer>
></http:>