![]() ![]() This article is about how I used OllyDbg in such an emergency to quickly reverse-engineer OllyDbg (partially), save the data hanging by a thread and develop a recipe for actions in case of such disasters. This is a waste of time and a monstrously demotivating factor, from which one gives up and turns pale. You systematically scout the essence of procedures / functions and variables and give them names that reflect your understanding of their purpose.Īnd now, after a few hours (or even days) of work, when you figured out and signed hundreds, or even thousands of procedures and variables, OllyDbg suddenly freezes or crashes, taking away all your work (which may include not only labels and comments in large numbers, but also breakpoints and modifications placed in the right places). If you use OllyDbg not for debugging your own applications for which you have debugging information, but for reverse engineering or third-party research, your typical activity is delving into the machine code of someone else's product, understanding the essence of things that are happening and placing a large number of labels (labels ) and comments throughout the code, as well as data sections. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |