Me respondió la desarrolladora de statifier:
https://sourceforge.net/forum/forum.php ... _id=358807Esto es lo que dijo:
Statifier in nutshell work as following:
1) Run (I repeat: RUN) program to be statified under debugger till certain point.
This point is AFTER all shared libraries are loaded and relocated and JUST before their _init functions invoked
2) Dump process memory and registers to the disk.
3) From data collected in 2) and some processor specific starter (part of statifier package) create statified executable.
Whole purpose of the starter is restore registers as they were, and jump to the address were execution was stopped by debugger.
As you can see, RUNNING program is essential part of the process.
And it can't be done in cross-build environment

((
So as I see you have following options:
1) Struggle with static build in the cross-compiling environment
2) Struggle with static build in the native environment (you can use QEMU to emulate arm)
3) Try to port statifier to ARM yourself. (I tried my best - and wasn't able to

(
4) Try to use Ermine (
http://magicErmine.com).
Ermine commercial, but it support ARM.
Also Ermine much better work on system with memory randomization
Statifier and ermine comparison can be found here:
http://www.magicermine.com/products.htm ... comparison Voy a ver si puedo hacer algo haciendo que statifier use qemu para correr el programa...
A veeer...
homer@head:~# ln -s /dev/null /dev/brain
homer@head:~# doh!
bash: doh!: command not found
Connection to head closed.