if you are familiar with c/c++, you may notice the macro way of optimization sometimes should duplicate the same chunk of code for a function, like strlen() or something rather simple; a popular macro style "function" called from many places in your code may also produce such "chunks".
some people like to "#include" c/c++ source code into their parent files to build something, so that it also generates many "chunks" of function dups.
how do you call a function from outside if it is static ? i am afraid these static functions might also become "chunk" if they are linked from different object modules.
Quote:
|
Originally Posted by Git
I notice sometimes when disassembling with IDA that sometimes a function is spead all over the place in FUNCTION CHUNKs. Is this an artifact of IDA or do some linkers really spread a function/procedure over many places?. I like to make things clear by using local labels and this makes it impossible. Is it maybe a result of languages that allow local procedures?
Git
|