On 12/02/2013 09:50 AM, Bukuli Norbert wrote:
Program received signal SIGILL, Illegal instruction.
[Switching to Thread 338]
0x4800ce74 in ?? ()
(gdb) bt
#0 0x4800ce74 in ?? ()
#1 0x0ff98534 in ?? ()
#2 0x0fe17a68 in ?? ()
#3 0x480eba4c in ?? ()
(gdb) info sharedlibrary
From To Syms Read Shared Object Library
0x00001ff0 0x0001b014 Yes
/opt/eldk-5.4/powerpc/sysroots/powerpc-linux/lib/ld.so.1
0x00100360 0x00100648 No
/srv/tftpboot/172.31.2.11/lib/modules/3.8.13/vdso/linux-vdso32.so.1
0x0ff979b4 0x0ff9e948 No
/opt/eldk-5.4/powerpc/sysroots/powerpc-linux/usr/xenomai/lib/libpthread_rt.so.1
For some reason, it looks like the program flow jumps to a weird
location. Assuming this backtrace is right, the last location that would
make sense seems to be frame #1 at 0x0ff98534 in libpthread_rt.so.1,
which is Xenomai's POSIX interface library.
- could you please make a full disassembly of libpthread_rt.so.1
accessible via pastebin?
- we already had these kinds of events a couple of times on different
architectures with new gcc releases due to, either broken TLS code
generation by gcc, or some weaknesses in our inline syscall trampoline
code with respect to expressing constraints. Is --with-__thread enabled
when configuring the Xenomai build for libaries and programs?
--
Philippe.
_______________________________________________
Xenomai mailing list
Xenomai@xenomai.org
http://www.xenomai.org/mailman/listinfo/xenomai
