Open GoogleCodeExporter opened 9 years ago
Hm. I think we *can* implement this eventually, but not with the highest
priority.
Let's have a look how hard this stuff is to port...
Original comment by thomasdu...@google.com
on 21 Aug 2012 at 8:19
Is it possible to explain the use case a bit more ? I am not sure I understand
it yet.
Original comment by thomasdu...@google.com
on 21 Aug 2012 at 8:29
With, for example, Windows executables chances are high that one can use FLIRT
signatures and TIL files to get library functions sorted out and documented.
In the embedded field this is not so easy. I'm talking about the smaller MCU's
like the Cortex M variants used without an operating system. Most of the time
the compiler is not identified or even available. Often the chip manufacturer,
the compiler vendor and other parties all have differing libraries for the same
purposes. Also every developer compiles these libraries with his individual
optimisation settings. Can't use FLIRT in this cases. I'm setting for example
the library function flag and function type manually when I stumble upon one.
But that's only my use case. Copying the function type should be useful for all
users.
The corresponding IDC functions would be: (I'm not knowledgeable about the SDK
functions)
GetFunctionFlags() http://www.hex-rays.com/products/ida/support/idadoc/337.shtml
GetType() http://www.hex-rays.com/products/ida/support/idadoc/172.shtml
used with the functions start address, which return a long and a string that
hopefully could be stored in your binexport data.
This could even be extended by using GetFlags() for the function start address:
GetFlags contains the info if a name is entered by a user or autogenerated.
And furthermore GetFlags and GetType for all addresses.
Hope this explains it better, Stefan
Original comment by L783x...@gmail.com
on 21 Aug 2012 at 10:56
Original comment by timkor...@google.com
on 9 Oct 2012 at 9:56
Original issue reported on code.google.com by
L783x...@gmail.com
on 20 Aug 2012 at 3:48