{"id":469,"date":"2007-10-30T21:45:02","date_gmt":"2007-10-31T04:45:02","guid":{"rendered":"http:\/\/multimedia.cx\/eggs\/the-quest-for-decompilation\/"},"modified":"2007-10-30T21:45:02","modified_gmt":"2007-10-31T04:45:02","slug":"the-quest-for-decompilation","status":"publish","type":"post","link":"https:\/\/multimedia.cx\/eggs\/the-quest-for-decompilation\/","title":{"rendered":"The Quest For Decompilation"},"content":{"rendered":"

Every now and then, someone comes along and writes a short novel of a comment on an older post. Such was the case when Sean Barrett<\/a> used the occasion of my What RE Looks Like<\/a> post to take three hours of his rather busy life<\/a> and compose a “symbolic executor” — a basic block decompiler. It’s a valiant effort and I would like to try my hand at it, as with all RE tools. I am having trouble compiling the source he posted (I converted CR format, but I am still having trouble with missing symbols from his custom library-in-a-header-file). It works on Microsoft-compatible disassembly output but probably would not be too hard to adapt for ‘objdump -Mintel’ in the GNU toolchain.<\/p>\n

Many people have gone down this basic block disassembly road. The details are hazy but I seem to recall that I have made the journey as well. It’s a good thing I keep this blog as a journal. I guess the reason I can’t remember what my experiment was called is because it was the “Unnamed RE Project”<\/a>. It looks like all I accomplished there was straight ASM -> C translation without any effort at higher level language abstraction.<\/p>\n

Anyway, I still maintain that figuring out the overriding purpose of these basic blocks is not the biggest challenge in traditional binary reverse engineering– indeed, I personally consider it the most interesting part. No, what I think is the toughest part is figuring out — or more likely guessing<\/em> — what the sometimes hundreds of referenced variables are actually used for, and assigning them appropriate names. The biggest nightmare is when functions pass around multiple gigantic nested structures and actually use a bunch of variables within.<\/p>\n

In other words, true understanding<\/em> of the underlying algorithm is the goal. But, Sean, I still want to try your tool.<\/p>\n","protected":false},"excerpt":{"rendered":"

Every now and then, someone comes along and writes a short novel of a comment on an older post. Such was the case when Sean Barrett used the occasion of my What RE Looks Like post to take three hours of his rather busy life and compose a “symbolic executor” — a basic block decompiler. […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[46,277,47],"class_list":["post-469","post","type-post","status-publish","format-standard","hentry","category-reverse-engineering","tag-intel-x86","tag-reverse-engineering","tag-sean-barrett"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t