We're working on a C program compiled with arm-eabi-gcc under Linux.
We're using a dump of a large structure and we're having problems determining at which adress we should read various fields of our structure (like 50 of them), (memory alignement and padding aren't so predictable to me).
Is there any way to get the memory mapping of the structure produced by a our compiler. An option in gdb? Or any tool helping us find the correspondance between fields and adress in the dump?
You can do it from a C program using the standard
offsetof()
macro, defined instddef.h
. However I'm not sure this is what you want, since you may be unable to run it (compiling it on the host will likely return wrong offsets).However, you may be able to employ some hacks to get the offset from a compiled binary without executing it. Maybe assign a static variable the offset value, and find some way of getting its value.
Seems to me you could write a bit of code like this for the required fields
to calculate the offset in bytes in this compile situation.
This should account for any alignment issues the compiler has.
You can do it with
gdb
. As an example, I'll use this source:Loading up the binary in
gdb
:UPDATE:
If you need to do it for a large number of fields, then you may find it handy to use GDB's new python interface (you'll need a recent version of GDB to use it, I'm using 7.4). I've created offsets.py:
Then you can add to your .gdbinit:
Then using it in GDB, like:
This script makes a few simplifying assumptions, like that you don't use bitfields, and it doesn't dig into nested structs, but those changes are3 fairly straightforward if you need them.