0

When trying to debug a program using the x64dbg and in a specific step, the following problem happens:

Is that mean that the program has an anti-debugger?
if not, why when debugging the program and in a specific step that problem happen?

3
  • The message itself it's not an anti-debug measure. it's just telling you that you have a debugger attached (x64dbg) and you cannot attach another one. Dec 4 '21 at 15:57
  • @PawełŁukasik: Thank you, but there is no other debugger attached to that program except x64dbg (Just one debugger attach to the program).
    – Lion King
    Dec 4 '21 at 17:12
  • Exactly, so you can't attach VS as a second debugger. Dec 5 '21 at 7:13
1

It seems that an exception happens in the program you’re debugging but is not handled by the debugger, so it escapes to the OS-wide exception handler (WER) which offers you to handle it with the visual studio debugger, but this is not possible because it’s already being debugged by x64dbg so you get this error message. You have two options:

  1. Edit x64dbg exception settings to make sure no exceptions are ignored so you can catch it in x64dbg and debug the reason. If the program has its own exception handler, let the exception happen, step through handler and find out why it’s not being handled properly.
  2. Detach x64dbg and debug the exception in Visual Studio.

However, it is indeed possible that the program has some kind of anti-debugging technique which allows exception to escape to the OS instead of catching it in the debugger.

1
  • But the program is working well in normal mode without any problem. also, x64dbg doesn't ignore any exceptions look at this screenShot. I think that is indeed possible that the program has some kind of anti-debugging technique as you said.
    – Lion King
    Dec 4 '21 at 20:39

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.