Hi,
To find out an offending instruction it is needed to create a simple
console app. Compile it with the -gl switch and run in the Android
console. You will get a stack back trace. If the instruction in the RTL,
it is needed to recompile it with the -O- -g switches.
Yury Sidorov,
j...@cp-lab.com
On 12/25/2014 2:06 AM, peter green wrote:
Sergio Flores wrote:
Eg: Calling lnxp1(x) with x>1 results in a SIGILL crash.
.....................
I've got an Android app in Play Store with around 300 thousand
downloads, and from what I've gathered, this crash happens in any
Tegra based device, and only on those.
AIUI many tegra devices don't support neon, I wonder if a neon
instruction is being used either because of incorrect compiler settings
or because of incorrect inline assembler code.
If this was happening on regular linux i'd suggest using gdb to get a
backtrace and a dissasembly of the sigill location but i'm not sure how
possible that is on andriod or how easy it is to get a suitable tegra
device running regular linux to experiment on.
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
_______________________________________________
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-devel
