- 
                Notifications
    
You must be signed in to change notification settings  - Fork 1.4k
 
call int80 callback from x86_64 syscall instruction #2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| 
           this looks good. can you please add a sample with SYSCALL instruction to  thanks.  | 
    
| 
           Added SYSCALL test in   | 
    
call int80 callback from x86_64 syscall instruction
| 
           merged, thanks. do you think that we should do something so the callback knows that this comes from   | 
    
| 
           It's better to be explicit, but this method does work for me right now. The ABI doesn't change in the handler either way afaik. I'm not sure what the alternative would look like. Maybe a non-interrupt handler that's just for SYSCALL-like instructions?  | 
    
| 
           i just committed a change to handle SYSCALL/SYSENTER instructions separately, so we do not share the callback with interrupts: e1baf2f. @lunixbochs: with this you will need to modify your usercorn code accordingly. thanks.  | 
    
Pulling in from unicorn-engine to my private repo
Merge pull request #2 from unicorn-engine/master
[afl++] fix segfault (using input buf after unmap)
…size (unicorn-engine#2…" (unicorn-engine#2220) This reverts commit c8bc9eb.
If there's an interrupt callback registered, this forces the x86_64
syscallinstruction to simulate anint $80callback and advance PC.