@aluhrs13 Hey, I'm trying to switch to preview, but I've noticed that you can't control execution in breakpoints anymore. For example, I'm used to doing bp kernel32!CreateFileA "gu; j (@eax == -1) ''; 'gc'" to break after a failed call.. how would you achieve that?
-
-
That nested 'gu' inside the breakpoint command looks a bit dicey. I'd probably set a conditional breakpoint on the ret in ntdll!NtCreateFile. (The condition needs to be <0 there, because it's an NTSTATUS.)
-
Well yeah, you can uf and manually find all the rets. That's a *lot* of work, and you're probably going to miss some and get confusing results. That's why the gu trick worked so well.
- 1 more reply
New conversation -
-
-
Missed your first tweet. Does this work for you with a recent version of old WinDbg (https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewSDK …)? The underlying engine that's doing these command parsings is exactly the same between the two so I wouldn't expected this to be a Preview specific bug.
-
Yes, looks like the same engine version - it's worked for years in classic windbg (I remember doing it since XP, at least), but Preview just prints errors about altering control flow.
- 1 more reply
New conversation -
-
-
Maybe another shower? ;)
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
I filed a few other feedback reports on things that used to work but don't anymore.