sstrato Posted December 30, 2015 Posted December 30, 2015 (edited) In x32 and x64 navigation keys up and down do not work in the window references and the window symbols. In X32 when patched in some directions out the window. The instruction is patched correctly. Edited December 31, 2015 by sstrato
mrexodia Posted January 7, 2016 Author Posted January 7, 2016 On 30 December 2015 at 9:40 PM, sstrato said: In x32 and x64 navigation keys up and down do not work in the window references and the window symbols. In X32 when patched in some directions out the window. The instruction is patched correctly. Thanks for the report. I will look into it. This warning message is meant to help you if you try to assemble "jmp x" where x is not pointing to a valid memory location or a memory location that is marked as non-executable. This behavior has been fixed and a new snapshot should be available soon. 2
Hypnz Posted March 19, 2016 Posted March 19, 2016 Hi. Newest snapshot have issues with breakpoints. Sometimes doesn't break. Anyone can confirm this?
sstrato Posted March 19, 2016 Posted March 19, 2016 (edited) From this update do not work properly ((#373 (05-mar-2016 13:03:43) (DBG: implemented caching (lookup in the memory map))). Edited March 19, 2016 by sstrato
sstrato Posted March 19, 2016 Posted March 19, 2016 the first time you run the program breakpoints work properly if recharging the program and rerun the breakpoints of the libraries do not work. If you revert back cache modification work (tested).
mrexodia Posted March 19, 2016 Author Posted March 19, 2016 Okay, thank you very much! I disabled caching for most part now, there might still be some issues with disassembling in newly allocated pages but this was expected behavior.
sstrato Posted March 19, 2016 Posted March 19, 2016 (edited) From esta big update (#204 (24-nov-2015 1:57:45)) it is impossible to erase the HBP placed in memory (Outside libraries and program), without parecece grave But it is annoying. Anyway they are inactive and can not be used. Edited March 19, 2016 by sstrato
mrexodia Posted March 20, 2016 Author Posted March 20, 2016 @sstrato Confirmed and fixed those issue(s). Thanks a lot for the report! Now 'inactive' breakpoints are shown in a GUI and you should be able to manipulate them normally (enable/delete). 1
sstrato Posted March 20, 2016 Posted March 20, 2016 9 hours ago, Mr. eXoDia said: @sstrato Confirmed and fixed those issue(s). Thanks a lot for the report! Now 'inactive' breakpoints are shown in a GUI and you should be able to manipulate them normally (enable/delete). They seem to work fine now, thanks great job.
sstrato Posted March 21, 2016 Posted March 21, 2016 You can highlight Regex search again. Normal search: Regex search:
Cthulhux Posted April 8, 2016 Posted April 8, 2016 Hi, just registered to say "Thank you!" for x64dbg. And I already have a small feature request: Maybe the strings from a file should be cached somewhere so they are not "processed" again every time I want to start a string search?
mrexodia Posted April 11, 2016 Author Posted April 11, 2016 On 4/8/2016 at 10:06 PM, Cthulhux said: Hi, just registered to say "Thank you!" for x64dbg. And I already have a small feature request: Maybe the strings from a file should be cached somewhere so they are not "processed" again every time I want to start a string search? If you search for strings you can go back to the reference tab and see your old results there.
sstrato Posted April 17, 2016 Posted April 17, 2016 Unable to save patch introduced at the end of the file without code area. Example: no-patch.wmv
mrexodia Posted April 19, 2016 Author Posted April 19, 2016 @sstrato are you sure there is space free there? A bug was found in the RVA <-> Offset conversion but most executables simply don't have space after the 'NOP' that you saw as last instruction.
sstrato Posted April 19, 2016 Posted April 19, 2016 1 hour ago, Mr. eXoDia said: @sstrato are you sure there is space free there? A bug was found in the RVA <-> Offset conversion but most executables simply don't have space after the 'NOP' that you saw as last instruction. If there is free space. Tested with several executables, all with free space at the end of the section of the .text section. OllyDbg if allowed.
mrexodia Posted April 22, 2016 Author Posted April 22, 2016 @sstrato Do you maybe see the bug in this conversion code? https://bitbucket.org/titanengineupdate/titanengine-update/src/941f39131757a76867176ccd256876c4e776a3cb/TitanEngine/TitanEngine.PE.Convert.cpp?at=master&fileviewer=file-view-default#TitanEngine.PE.Convert.cpp-106 Greetings
mrexodia Posted April 22, 2016 Author Posted April 22, 2016 @sstrato It should be fixed now. Here is the corresponding issue https://github.com/x64dbg/x64dbg/issues/356
Artic Posted May 12, 2016 Posted May 12, 2016 the string search is working a bit slower in the last version from 1. May, it hangs at a percentage. i do most of the time search for strings in one module, maybe it is normal, but i remember in a build from April, it was much faster.
mak Posted May 12, 2016 Posted May 12, 2016 Does anybody have any contact with the author? It would be cool to ask him to publish the source code in order to someone could make a script editor for x64DBG debugger? OllySubScript сommands can be added to the list, removing completely the same lines from the list does not work, there is only forcible manner. x64DBG_SubScript - Generally it would be useful to users.
kao Posted July 13, 2016 Posted July 13, 2016 @Hatschi: considering that you can't create unmanaged exported functions in C# without extra hacks (like https://www.nuget.org/packages/UnmanagedExports ), people are quite unlikely to port SDK to C#. But if you wish to do that yourself, that might be a pretty cool weekend project..
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now