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 :)

deroko: You can use the option 'Skip INT3 stepping' (https://i.imgur.com/JzPDRws.png), or manually use the `skip` command to achieve what you want.

Respect for your work.

Ah sweet, had no idea this options is doing this. Tnx :)

Cool!
Wish x64dbg could be cross-platform.

I was trying to use this debugger the other day and run over a strange issue.

I was not able to make it ignore an exception thrown by the application (ExceptionCode: C0000005), as far as I can tell its part of a anti reverse engineering technique. in IDA the same exception gets thrown but there when I encounter the first one i can tell it to ignore all subsequent once.

I tried to uncheck all the "break on" checkboxes in the options as well as adding last exception and/or add 00000000-ffffffff to the excluded exceptions list but still it did not ignore the exception. I wonder if there is a bug (I was using the latest build as of yesterday) or if I missed some option.

If its the later than I would appreciate being pointed towards it and if its the former than a fix would be much appreciated to :)

@sendersu Just followed the UPX tutorial, works like a charm.

I'll be working with some more advanced packers soon, after nailing down UPX. Mr. Exodia has done some awesome work with x64dbg... no doubt.

anyone know why DataCopy was removed. last version with it is snapshot_2018-04-05_00-33

A quick skim over the merge requests and commit log show it was merged and combined a single editor. (Hex editor / string editor / data copy dialog into one. https://github.com/x64dbg/x64dbg/pull/1941)

Great tool, many thanks for it!

For anyone else interested:

There had been a bug with remapping code (including Blizzard games) that was fixed with this commit: https://github.com/x64dbg/x64dbg/commit/d50675ca025e3494de683d8510a681551e92c8ab

screenshot is deleted. I wish we had an upload section for files to stay there for a long time. I am a member of digital networks forum for more than 19 years and most of the uploaded files are still inside the upload section.

You can find screenshots on their homepage if you are looking for examples of what it looks like:
https://x64dbg.com/

Wow great job. I liked DLL debugging feature. Good for Wibu codmeter people.

Hello mr.exodia ,
are you planning to add such functionality? https://github.com/x64dbg/x64dbg/issues/2067 very need it.

And can you give me btc wallet for donate? You gave it to me on another forum (exelab) six months ago, but that forum died, but I don’t know how to write it in a personal note (sorry for the bad English).

The BTC wallet to donate is linked on the main page of x64dbg.