Search type Search syntax
Tags [tag]
Exact "words here"
Author user:1234
user:me (yours)
Score score:3 (3+)
score:0 (none)
Answers answers:3 (3+)
answers:0 (none)
isaccepted:yes
hasaccepted:no
inquestion:1234
Views views:250
Sections title:apples
body:"apples oranges"
URL url:"*.example.com"
Favorites infavorites:mine
infavorites:1234
Status closed:yes
duplicate:no
migrated:no
wiki:no
Types is:question
is:answer
Exclude -[tag]
-apples
For more details on advanced search visit our help page
Results tagged with Search options answers only user 60

An open-source x64/x32 debugger for windows with UI inspired by OllyDbg.

0
votes
Normally the debugger should pause at the location where breakpoint is triggered, or you can use "jump to EIP" or similar command to navigate to the instruction being executed (which should be the one …
answered Oct 20 by Igor Skochinsky
1
vote
Going by the similar question for OllyDbg, it seems you should be able to achieve it by using Conditional Tracing. The doc also mentions: You can start a conditional tracing by “Trace over until …
answered Nov 22 by Igor Skochinsky
1
vote
Searching for RVA as bytes works for x86 code since RVA is encoded directly in the instruction. However, as you noticed, it does not work on x64 where you instead have a RIP-relative offset which obvi …
answered Oct 3 by Igor Skochinsky
1
vote
It seems you're looking at a Wow64 syscall stubs in 32-bit ntdll.dll. WOW64 can use a special value in the high part of the syscall number for so-called Turbo thunks. From WoW64 internals by "wbenny": …
answered Sep 5 by Igor Skochinsky
1
vote
It’s hard to say for sure without full binary or all called functions but going by the debugger screens it looks like the argument is pointer to a structure with layout similar to the following: str …
answered Apr 23 '18 by Igor Skochinsky