Jump to content
View in the app

A better way to browse. Learn more.

Tuts 4 You

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Feature suggestions

Featured Replies

Posted

Hello everyone,

As Artic suggested, this topic is for feature suggestions. Post anything you wanna see in the next release here. Make sure to also post it over at https://bitbucket.org/mrexodia/x64_dbg/issues/new

Greetings,

Mr. eXoDia

  • Replies 180
  • Views 60.4k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • What about a function like collapse when RSP point to a system call? I have made a sample to make it clear. I think that can be one of the cleanest solution without wrongly show in the stack the

  • Not sure if these have been requested:   1. Ability to sort the symbols (exports) by name 2. Ability to search for binary strings 3. Ability to set a memory breakpoint in the memory map window 4.

  • Possibillity to write/edit script in script tab would be great.

Posted Images

hello, is that possible searching Chinese strings? if you can find some source code in bbs.pediy.com

 

when you see below OllyDBG picture, you will see 4 windows with red words explained. but what other windows called in OD and x64DBG?

 

1. Disassembly window
2. Registers window
3. Dump window
4. Stack window
5. How to call this window?

 

when will make it work?

 

Olly1.png

Edited by chixiaojie

suggust:

double click EIP will go to current EIP in CPU window, just like OD. 

 

Greetings,rxz

Edited by rxzcums

  • Author

@chixiaojie: Searching for UNICODE strings is possible, but currently unsupported, because x64dbg is 100% ASCII based. Rewriting for UNICODE is possible and I will work on this, but first I want to solve various other things.

And for the rest of your suggestion, what's the deal with all these windows? I attached screenshots of all views available in x64dbg in the current dev build.

Greetings,

Mr. eXoDia

x64_dbg_pictures.rar

Not sure if these have been requested:


 


1. Ability to sort the symbols (exports) by name


2. Ability to search for binary strings


3. Ability to set a memory breakpoint in the memory map window


4. Quicker method to add exceptions to a new session


5. A call stack window similar to Olly's K tab


6. Information appearing in what is called the "data" window just below the disassembly window


7. Ability to navigate forwards and backwards in the disassembly window using the '+' '-' keys


similar to Olly.


8. Binary edit in disassembly window (context window)


9. Search for all intermodular calls in disassembly window (context menu)


 


Also, nice job on the gui and debugger.


 


BR,


 


CZ


  • Author

@CondZero: some are already implemented (like the +/-), others will go directly to the todo list.

Greetings

  • 2 weeks later...

an update checker would be awsome! :)


 


Greetings


It would help if you add a plugin that reads the script Ollydbgscript 1.82!


  • Author

@kassane: 100% ODBGScript/OllyScript support will never be implemented, we might do a converter in the future though. There is a script language implemented, it also directly supports stuff like this:

mov page,[esp+4]+10002:[kernel32:GetProcAddress+21]=0x9090bp LoadLibraryA
A converter tool would require all variables used in the ODBGScript to be prefixed with 'Script_' or something else, because x64_dbg would error on the following script:
gpa "GetProcAddress","kernel32.dll"mov GetProcAddress,$RESULT <- invalid dest "GetProcAddress"
GetProcAddress is already an export, so you cannot move anything to it.

Prefixing the variable could make most stuff working.

Read the following page for more information about the allowed input types in x64_dbg: http://x64dbg.com/help/scr/Input.htm The following page is about what kind of calculations can be done and used directly as input: http://x64dbg.com/help/scr/Calculations.htm

All the possible (script) commands can be found at http://x64dbg.com/help/scr/Commands.htm

If you know any command that you would like to see implemented from ODBGScript, please create an issue at http://issues.x64dbg.com or post a new thread here.

Greetings,

Mr. eXoDia

Edited by Mr. eXoDia

  • Author

Not sure if these have been requested:

 

1. Ability to sort the symbols (exports) by name

2. Ability to search for binary strings

3. Ability to set a memory breakpoint in the memory map window

4. Quicker method to add exceptions to a new session

5. A call stack window similar to Olly's K tab

6. Information appearing in what is called the "data" window just below the disassembly window

7. Ability to navigate forwards and backwards in the disassembly window using the '+' '-' keys

similar to Olly.

8. Binary edit in disassembly window (context window)

9. Search for all intermodular calls in disassembly window (context menu)

 

Also, nice job on the gui and debugger.

 

BR,

 

CZ

1. Implemented in the current dev version.

2. ctrl+b (you cannot yet search the whole process)

3. yep, can be done already

4. could you elaborate on that? there is an 'Add Last Exception' button in the exception settings dialog

5. yep, we're working on it

6. also working on that :)

7. yep, it's implemented

8. yep, also implemented

9. yep, implemented as well

Thanks for your suggestions.

Greetings,

Mr. eXoDia

EDIT: oops, didn't see I already replied here, could this be merged with my previous post please?

Edited by Mr. eXoDia

Is there an option for repeatable comment for the same instructions? What I want to do is to be able to comment one line and that x64dbg repeats it for all instances of the same command.
Example:

401000 call 12345678     ; call to some function...401070 call 12345678     ; call to some functionor401000 push 12345678     ; push some string...401050 push 12345678     ; push some string

Also do you plan to keep compiled versions of plugins or are we supposed to install VC compiler to get working plugins? I was looking for plugin to import map files but found only link to src on x64dbg site.

  • Author

@ToMKoL:

No, there is no option to do this.

Plugins are separate from x64dbg, so I cannot provide support for them. If you need a plugin, ask the author, which is not me in most cases.

Greetings

Thanks for answer. Do you have plans to implement 'copy data' (mainly strings) from dump window? 


  • Author

@ToMKoL: Yes


x64dbg assembling - CHECK! thanks alot! Mr. eXoDia


 


i feel honored, thanks for mention me in the Special Thanks!


Edited by Artic

Hi, I want to know, is it possible to add feature that allows to debug program which  works as a service?


Edited by Siarogak

  • Author

@Siarogak: You should be able to attach to the service process (although attaching is broken in the current release, it should be fixed by the next release).

I know, but some checks can be performed when the program starts, and there is no sense in debugging when the programm runs. 


Edited by Siarogak

  • Author

@Siarogak: And when you open the application in the debugger it doesn't start the service? You could change the EP bytes to EBFE and attach the debugger after it started. In that way you can also debug the initialization routine.

update checker and save:prop:

  • Author

@FILIPOVIC: Update checker is implemented in the current dev version and save is implemented.

really good news @eXoDia :) if you need a tester, i would like to test.


copying code from disassembly window


  • 2 weeks later...

You want to make your software in multi languages​​?


is it possible to make hints and the autocompletion in the command line for API's, like you did it for commands?


Edited by Siarogak

Create an account or sign in to comment

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.