![]() |
|
|||||||
| View Poll Results: Would you use this debugger? | |||
| Yes (mainly x32) |
|
97 | 29.04% |
Not at all
|
|
25 | 7.49% |
| Yes, if it gets better (please post feature suggestions) |
|
90 | 26.95% |
| Yes (mainly x64) |
|
122 | 36.53% |
| Voters: 334. You may not vote on this poll | |||
![]() |
|
|
Thread Tools | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Thank you
this would be one of the features I was missing
__________________
http://accessroot.com |
|
#2
|
|||
|
|||
|
I am not olly pro, so let me ask few questions about x64dbg?
1. Minor. Does it have sync option between tabs. So, if I stopped at some EIP I can switch to memory map and see synced memory region line active, not the top one. Example: I stopped at 18001234 switch to Memory Map and see 18000000 active and it is .text of test.dll 2. Minor. Is there an option show Export names in comments? Example: I stopped at 18001234 and see in comments column: test.dll!DllMain 3. Major. How can I point DLL of interest, but start test.exe instead of DLLLoaderXXX.exe? I changed the command line and restarted debug, but the command line reset as well. I suppose it changes only environment data, not the .exe. 4. Crit. Extend the Q3. Is it possible to debug 64-bit DLL and use .net .exe as loader? If I try to point .exe as target x64dbg says "Use 32-bit debugger". I think it is not my case. 5. Idea. Any plans to make it interactive like IDA? Or at least split the code flow blocks with empty lines. |
|
#3
|
|||
|
|||
|
I am trying find the encryption seeds from a 64bit daemon, and have only experience using Ollydbg, which doesn't debug x64 binaries.
So I started using x64_dbg, but this debugger does not have a field where you can input any arguments such as "-t computer-name 4 –c license.lic" I tried x64_dgb "C:\FullPathTo\File.exe" parm1 parm2 -3 -4 -debug x64_dgb "C:\FullPathTo\File.exe" -t computer-name 4 –c license.lic and using InitDebug & setcommandline, but none of these pass the arguments -t computer_name 4 -c license.lic to the debugger Can anybody tell me how to pass on arguments to this debugger? rgds |
|
#4
|
|||
|
|||
|
i need an answer too.
as i think it is impossible to pass arguments now, but maybe are some plans to add this possibility to x64_dbg? or advise other debugger for x64. |
|
#5
|
|||
|
|||
|
Any help please?
|
|
#6
|
|||
|
|||
|
Just tested it on x64 - Google Chrome. Immunity crashed for some reason, but this helped me a lot!
|
|
#7
|
||||
|
||||
|
I always use your x64_dbg.
It helped me a lot! It's a great and a masterpiece creation. Thank you mr.exodia... Best regards, -=yoza=- |
|
#8
|
|||
|
|||
|
Quote:
Certainly helps a lot , with newer programs whose anti-debugging mechanisms simply check for OLLY , but don't check for this debugger ![]() Please continue your development on this mr.exodia ... |
|
#9
|
|||
|
|||
|
I wonder if it is possible to call a dll export when we load dll in x64dbg(similar to olly).
Does anyone know if this is possible? I were not able to find this myself.
__________________
I should look out my posts,or JMI gets mad on me!
|
|
#10
|
|||
|
|||
|
May be use "Set origin here" to change EIP after break on retn in DllMain.
|
|
#11
|
|||
|
|||
|
Hello,
Syoma is right, you can do something like setting the EIP. Another method is to simply code a small DLL loader that does something like this: Code:
#include <windows.h>
int main() {
HINSTANCE hInst = LoadLibraryA("x32gui.dll");
typedef int (*GUIGUIINIT)(int, char**);
GUIGUIINIT _gui_guiinit = (GUIGUIINIT)GetProcAddress(hInst, "_gui_guiinit");
int result = _gui_guiinit(0, nullptr);
return 0;
}
Mr. eXoDia |
| The Following User Says Thank You to mr.exodia For This Useful Post: | ||
b30wulf (09-24-2015) | ||
|
#12
|
|||
|
|||
|
Quote:
Thanks for reply. These 2 ways were somehow obvious and I already have done it this way. But I thought there may be an easy for it like olly, because it somehow a useful option for debugging DLLs. Maybe I write its plugin my own. Regards
__________________
I should look out my posts,or JMI gets mad on me!
|
| The Following User Gave Reputation+1 to Hero For This Useful Post: | ||
| The Following User Says Thank You to Hero For This Useful Post: | ||
b30wulf (09-24-2015) | ||
|
#13
|
|||
|
|||
|
Yea, a plugin sounds cool. Feel free to drop me a message if you need help.
|
|
#14
|
||||
|
||||
|
Just a quick q, why not implementing python as script instead of developing own scripting language?
__________________
http://accessroot.com |
| The Following User Says Thank You to deroko For This Useful Post: | ||
Storm Shadow (10-17-2015) | ||
|
#15
|
|||
|
|||
|
At the time it seemed more logical to do an olly script like language. Right now there is someone working on python.
|
| The Following User Says Thank You to mr.exodia For This Useful Post: | ||
Storm Shadow (10-17-2015) | ||
![]() |
| Tags |
| bit, debugger, x32, x64, x64_dbg |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Debug with x64dbg | dnvthv | General Discussion | 2 | 03-22-2025 21:49 |
| Add .lib file on x64dbg ? | LaDidi | General Discussion | 0 | 02-18-2022 14:39 |
| DBG2AP - x64dbg plugin | Agmcz | Community Tools | 1 | 06-15-2019 07:14 |
| nfd - x64dbg plugin | hors | Community Tools | 2 | 04-01-2018 08:18 |
| x64dbg python | Storm Shadow | Developer Section | 6 | 08-04-2017 15:29 |