As a debugging technique, I am trying to get the hook DLLs to trigger a debug break point. The DLLs are tested inside VMs (VMWare) and WinDBG is attached to the VM for kernel debugging/exe. This also allows me to somewhat debug the DLLs.
Does anyone know how I can trigger a debug break point from my DLL (in code, using DebugBreak() call), that does NOT send back the exception back to the app itself, forcing a close?
Namely, if my code calls DebugBreak() (even inside a try/except block), once I leave WinDBG, the exception gets propagated to the app the DLL is injected into
Getting a debug break point in WinDBG/VMWare
Re: Getting a debug break point in WinDBG/VMWare
I would have thought a try..except end (Delphi) or __try..__except (1) (C++) block would do the trick. If that doesn't work then I don't know.
Re: Getting a debug break point in WinDBG/VMWare
I actually don't have a Delphi, but C DLL, though the try/except is the same thing.
It doesn't work, once WinDBG is triggered, as soon as I am out of the DebugBreak() call, the exception gets propagated to the application, and is not captured by try/except.
It doesn't work, once WinDBG is triggered, as soon as I am out of the DebugBreak() call, the exception gets propagated to the application, and is not captured by try/except.