|
|
|||||||
| View Poll Results: Would you use this debugger? | |||
| Yes (mainly x32) |
   
|
93 | 28.79% |
Not at all 
|
  
|
24 | 7.43% |
| Yes, if it gets better (please post feature suggestions) |
  
|
89 | 27.55% |
| Yes (mainly x64) |
  
|
117 | 36.22% |
| Voters: 323. You may not vote on this poll | |||
|
|
Thread Tools | Display Modes |
|
#11
06-16-2018, 14:43
|
||||
|
||||
|
One thing I always wanted to ask for
 When I have __debugbreak() enabled and attach as JIT, x64dbg breaks always on this int 3, and even if you set new origin after int 3 it somehow restores exception back to int 3 and usually solution is to replace int 3 with nop. Olly and windbg tend to break after int 3 thus exception doesn't reacquier.This would be great imho
__________________
http://accessroot.com 
|
| The Following 4 Users Say Thank You to deroko For This Useful Post: | ||
| Tags |
| bit, debugger, x32, x64, x64_dbg |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| AdvancedScript x64dbg Plugin | ahmadmansoor | Developer Section | 14 | 10-15-2019 00:35 |
| DBG2AP - x64dbg plugin | Agmcz | Community Tools | 1 | 06-15-2019 07:14 |
| nfd - x64dbg plugin | hors | Community Tools | 2 | 04-01-2018 08:18 |
| CopyToAsm - x64dbg plugin | mrfearless | Community Tools | 0 | 03-04-2018 08:36 |
| x64dbg python | Storm Shadow | Developer Section | 6 | 08-04-2017 15:29 |
Threaded Mode