Jump to content
Tuts 4 You

Feature suggestions


mrexodia

Recommended Posts

  • Replies 180
  • Created
  • Last Reply

Top Posters In This Topic

  • mrexodia

    68

  • sstrato

    44

  • Artic

    14

  • Hypnz

    7

Top Posters In This Topic

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

Search constant in the CPU window does not work. Possible solution change order of parameters in line CPUDisassembly.cpp: original: DbgCmdExec(QString("findref %1, %2, 0, %3").arg(addrT

Yea, there are problems with when you try to follow an address that is too far at the end, it will not display so I decided to solve it like this until I properly fix it.   Always use the late

Posted Images

Dragon Palace

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 (see edit history)
Link to post
mrexodia

@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

Link to post
CondZero

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


  • Like 2
Link to post
mrexodia

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

Greetings

Link to post
  • 2 weeks later...
mrexodia

@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 (see edit history)
  • Like 1
Link to post
mrexodia

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 (see edit history)
Link to post

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.

Link to post
mrexodia

@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

Link to post

x64dbg assembling - CHECK! thanks alot! Mr. eXoDia


 


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


Edited by Artic (see edit history)
Link to post
mrexodia

@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).

Link to post
mrexodia

@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.

Link to post
mrexodia

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

Link to post

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


Link to post
  • 2 weeks later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...