From: Philippe Gerum <rpm@xenomai.org>
To: Bukuli Norbert <norbert.bukuli@mediso.hu>, Wolfgang Denk <wd@denx.de>
Cc: Xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] test suite programs crash with Illegal instruction on MPC5200
Date: Mon, 02 Dec 2013 10:15:22 +0100 [thread overview]
Message-ID: <529C4FAA.9080502@xenomai.org> (raw)
In-Reply-To: <20131202095057.175411b7.norbert.bukuli@mediso.hu>
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.
next prev parent reply other threads:[~2013-12-02 9:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-28 13:31 [Xenomai] test suite programs crash with Illegal instruction on MPC5200 Bukuli Norbert
2013-11-28 20:17 ` Gilles Chanteperdrix
2013-11-28 20:30 ` Gilles Chanteperdrix
2013-11-29 7:59 ` Bukuli Norbert
2013-11-29 7:45 ` Bukuli Norbert
2013-11-28 22:01 ` Philippe Gerum
2013-11-29 8:41 ` Bukuli Norbert
2013-11-29 8:41 ` Bukuli Norbert
2013-11-29 9:29 ` Philippe Gerum
2013-11-29 9:34 ` Philippe Gerum
2013-11-29 10:44 ` Bukuli Norbert
2013-11-29 10:27 ` Bukuli Norbert
2013-11-29 15:33 ` Philippe Gerum
2013-12-02 7:50 ` Bukuli Norbert
2013-11-29 22:53 ` Wolfgang Denk
2013-12-02 8:50 ` Bukuli Norbert
2013-12-02 9:15 ` Philippe Gerum [this message]
2013-12-02 9:24 ` Bukuli Norbert
2013-12-02 9:41 ` Philippe Gerum
2013-12-02 9:44 ` Bukuli Norbert
2013-12-02 9:58 ` Philippe Gerum
2013-12-02 10:16 ` Bukuli Norbert
2013-12-09 14:52 ` Bukuli Norbert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=529C4FAA.9080502@xenomai.org \
--to=rpm@xenomai.org \
--cc=norbert.bukuli@mediso.hu \
--cc=wd@denx.de \
--cc=xenomai@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.