I don't wanna be rude here but the question about passing arguments has been answered in this thread multiple times :)
Also check out the FAQ before you ask questions : http://faq.x64dbg.com |
excuse me for my carelessness.
thank you for your patience and link. |
Version 25 is out.
eXoDia added the search in memory feature. :) |
Quote:
It seems that OllyDbg 64 is dead; but hopefully we have x64_Dbg |
Quote:
A debugger on X64 from Oleh will be a good competitor alo. |
I agree with GIV. But x64dbg is open source so it gives space for expansion for advance programmers to make their private builds, to others a chance to learn debugging mechanism, and its regularly updating and getting better, so olly for now is still better choice for 32bit systems, mor or less because of its code analysis feature and wide range of plugins for noob and medium level users.
PS. My vote goes to x64dbg. For sure in a near feature it will overcome olly |
As for the function analysis (no stack/arguments yet) there is a nice command to try:
'anal' Greetings |
There are 16 pages gone n i dont wanna check one by one if its said or not
From last couple of days i am playing with it seems ok to be before it was scary I miss stack trace it doesnot show main modules calls like olly when we pause it any progress in it After that i found analysis ofcourse cant see any calls in subroutine from where it is getting called N yup last thing is that cant we enter call without any BP on it cus sometimes i dont get BP but i know the code is excuting assuming 32bit patch on olly assuming atleast close on x64 now i click enter on call444balbla but it dont enter untill BP comes and u press f7 i had to find those hexes from hex editors n manually patched it. Anyway it is going good n i appreciate exodia work +1 cus last time i tried alpha 21 i guess seems progress slowly but steady ;) |
Anal is command haha nice command i will try ;) oh man cant stop laughing ;)
|
@Jasi: Call stack is indeed broken. It will be fixed soon hopefully (still working on merging Nukem's branch). The second issue is kind of hard to understand for me. Could you make a video and upload it somewhere please?
Thank you. |
By second i mean taking example with olly
now when you load 32bit execu. in olly then on subroutines you find $ sign which means its another subrountine entry point and when you press right click and you can see the all calls which are pointing to this subroutine thats what x64dbg lacks hope its clear now like i never know when new subroutine starts i assume its starts from PUSH BLA BLA i assume not clear though until we trace it |
Hello,
Thanks for your feedback. For now you can find references to a subroutine by using Ctrl+R on the entry point of the call. Greetings |
just used this today (find refs) and it works perfect.
i love my x64dbg so much, thanks for all the work on this project. |
I love this debugger, it works great & it's good looking...
But more important it's open source and I learned a lot from the sources. I've used it to reverse a few programs and learn unpacking! |
it's very cool, it's my main debugger on x64
|
All times are GMT +8. The time now is 20:29. |
Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2024, vBulletin Solutions, Inc.
Always Your Best Friend: Aaron, JMI, ahmadmansoor, ZeNiX