Ollydbg Error Unable To Locate Data In Executable File
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and ollydbg copy to executable all modifications policies of this site About Us Learn more about Stack Overflow the ollydbg copy to executable missing company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags
Ollydbg 2 Save Executable
Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only
Ollydbg Save Exe
takes a minute: Sign up OllyDbg, don't get the option to copy to executable file up vote 3 down vote favorite Whenever I'm in OllyDbg and successfully finish editing the ASM code to my liking, I try to highlight all the modifications I've made and when I right click....I don't get the option to "Copy to Executable?" - Yet a lot immunity debugger unable to locate data in executable file of the tutorials I follow have this option, and they do it in the videos. Details: OllyDbg2 Windows 7 x86 Running OllyDbg as an administrator No plugins ollydbg share|improve this question asked Jul 29 '13 at 23:49 Justin 128413 add a comment| 1 Answer 1 active oldest votes up vote 2 down vote accepted One of two things happened if you cannot right click -> edit-> copy to excutable. You edited within the data section of the executable which it has nothing to copy then. You made your edits outside of the main module. If you edited any of the dll's then you cannot copy it to executable also. share|improve this answer answered Jul 30 '13 at 0:12 ObieMD5 2,2561824 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest Name Email Post as a guest Name Email discard By posting your answer, you agree to the privacy policy and terms of service. Not the answer you're look
Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies
Ollydbg Download
of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Reverse Engineering beta Questions Tags Users Badges Unanswered Ask Question _ Reverse Engineering Stack Exchange is a question and answer site for researchers and developers who explore the principles of a system through analysis of its structure, function, and http://stackoverflow.com/questions/17936118/ollydbg-dont-get-the-option-to-copy-to-executable-file operation. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Ollydbg 'Copy all modifications to executable' doesn't copy all modifications up vote 4 down vote favorite I'm editing executables on a(n) (almost) daily bases in Ollydbg and it is http://reverseengineering.stackexchange.com/questions/3579/ollydbg-copy-all-modifications-to-executable-doesnt-copy-all-modifications very annoying that the 'Copy all modifications to executable' doesn't work properly. All the code I edit in the .text section is copied to the new executable, but all the changes made to the .rsrc section (resources) is not copied. (Using 'Copy all...') To save my changes made in the .rsrc section, I need to select the modified code in this section and specifically click 'Copy to executable'. Is there a workaround to actually copy ALL modifications? ollydbg share|improve this question edited Feb 1 '14 at 11:44 Danyal 1316 asked Jan 29 '14 at 20:43 Dennis van den Berg 384 add a comment| 1 Answer 1 active oldest votes up vote 1 down vote You need two times to save the changes. Once for .text section and re-do for .rsrc section. Each time you use this option OllyDBG just save all change of the section that you use "copy to executable" share|improve this answer edited Feb 2 '14 at 16:37 answered Feb 2 '14 at 16:31 HamiD 514 @ Hamid ollydbg depends on analysis data to save all modifications and it does not
name was the error I got when I was trying to patch a simple application and tried to copy my modifications to the executable file. I was http://www.woodmann.com/forum/archive/index.php/t-9222.html wondering if there is any way to get it working even though this error seems to be hard to avoid. blabbererJune 24th, 2006, 09:02who is reporting that error ? windows, billgates's seceratary ? your cat ? if it was ollydbg reporting that error then that means you are modifying your executable over and above your raw size raw size will be in installments unable to of 0x200 bytes while virtual size will be in installments of 0x1000 bytes while mapping the windows loader will map all sections to the size of 0x1000 so there will be lot of space available to modify in memory but when writing back there isnt enough space so ollydbg will report that error try dumping your memory with ollydump with all the changes intact unable to locate or try adding a section at the end big enough to hold your modifications and trampoline there btw you could have searched this forum and could have found out all of this by yourself there are atleast 4 posts that return back if you tried searching "unable to locate data" of course google returns > 20,000 hits Results 1 - 10 of about 25,200 for unable to locate data ollydbg. (0.37 seconds PerkeleJune 25th, 2006, 16:47You're right, I was a bit in a hurry last time but I did a search and found out that it could easily be done through OllyDump (which I did then). The only problem now is that (after making the RAW size equal the virtual size) the executable no longer works Ricardo NarvajaJune 25th, 2006, 17:24you not only need raw size = virtual size you need add the bytes with a hex editor, the file is needed be increased , not only changin a value in the header the file grow, in a hex editor look the end of the section and add zeros, to complete till the size nedded. Ricardo Na