News:

Masm32 SDK description, downloads and other helpful links
Message to All Guests
NB: Posting URL's See here: Posted URL Change

Main Menu

How to replace Dr. Watson with OllyDbg?

Started by NoCforMe, February 05, 2022, 09:09:20 AM

Previous topic - Next topic

NoCforMe

I want Olly to come up when something crashes instead of Dr. Watson, which offers no interactive operation. I put Olly in the registry, under HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\AeDebug, and it does open on a fatal error, but there's no data from the actual application (or DLL) that caused the error. I think I need something on Olly's command line to connect to the failing code, but I can't find anything online about this. Odd, because I know other people use this in place of Dr. Watson or WinDebug.
Assembly language programming should be fun. That's why I do it.

jj2007

I assume you use Olly's version 2. Go to Options/Options/Just-in-time and click "Set OllyDbg". That's it.

In the unlikely case that you are a RichMasm user, and that Olly sits in \Masm32\OllyDbg\ollydbg.exe:

int 3  ; somewhere in your code launches Olly
; int 3  ; doesn't launch Olly
INT 3  ; doesn't launch Olly, but of course, the just-in-time debugger will take over at this point

NoCforMe

Assembly language programming should be fun. That's why I do it.