Igor’s Tip of the Week #143: Fixing wrong address references in the decompiler
When decompiling code without high-level metadata (especially firmware), you may observe ...
Igor’s Tip of the Week #142: Mapping local types
When working on a binary, you often recover types used in it from many sources:
Igor’s Tip of the Week #138: Pointer math in the decompiler
While working with decompiled code and retyping variables (or sometimes when they get typed by the ...
Igor’s Tip of the Week #120: Set call type
Previously we’ve described how to use available type info to make decompilation of calls more ...
Igor’s Tip of the Week #119: Force call type
When dealing with compile binary code, the decompiler lacks information present in the source code, ...
Igor’s Tip of the Week #118: Structure creation in the decompiler
We’ve covered structure creation using disassembly or Local Types, but there is also a way of doing ...
Igor’s Tip of the Week #117: Reset pointer type
While currently (as of version 8.1) the Hex-Rays decompiler does not try to perform full type ...
Igor’s tip of the week #108: Raw memory accesses in pseudocode
Sometimes in pseudocode you may encounter strange-looking code:
Igor’s tip of the week #107: Multiple return values
The Hex-Rays decompiler was initially created to decompile C code, so its pseudocode output uses ...
Connect with the community on
© 2024 Copyright Hex-Rays