All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Bukuli Norbert <norbert.bukuli@mediso.hu>
Cc: Xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] test suite programs crash with Illegal instruction on MPC5200
Date: Fri, 29 Nov 2013 10:34:55 +0100	[thread overview]
Message-ID: <52985FBF.8090608@xenomai.org> (raw)
In-Reply-To: <52985E94.4070101@xenomai.org>

On 11/29/2013 10:29 AM, Philippe Gerum wrote:
> On 11/29/2013 09:41 AM, Bukuli Norbert wrote:
>> (gdb) cont
>> Continuing.
>> warning: Could not load shared library symbols for linux-vdso32.so.1.
>> Do you need "set solib-search-path" or "set sysroot"?
>> warning: .dynamic section for
>> "/opt/eldk-5.4/powerpc/sysroots/powerpc-linux/usr/xenomai/lib/libpthread_rt.so.1"
>> is not at the expected address (wrong library or version mismatch?)
>> warning: .dynamic section for
>> "/opt/eldk-5.4/powerpc/sysroots/powerpc-linux/usr/xenomai/lib/libxenomai.so.0"
>> is not at the expected address (wrong library or version mismatch?)
>
> These warnings may trigger with recent broken gdbserver releases, let's
> ignore them.
> https://sourceware.org/ml/gdb-patches/2013-06/msg00054.html
>
>> [New Thread 280]
>>
>> Program received signal SIGILL, Illegal instruction.
>> [Switching to Thread 280]
>> 0x0fdf4e74 in ?? () from
>> /opt/eldk-5.4/powerpc/sysroots/powerpc-linux/lib/libc.so.6
>>
>
> (gdb) disass $pc-64 $pc+20
>
> would help at this point.
>
>> (gdb) bt
>> #0  0x0fdf4e74 in ?? () from
>> /opt/eldk-5.4/powerpc/sysroots/powerpc-linux/lib/libc.so.6
>> #1  0x0ffd8af8 in sched_setconfig_np ()
>>     from
>> /opt/eldk-5.4/powerpc/sysroots/powerpc-linux/usr/xenomai/lib/libpthread_rt.so.1
>>
>> #2  0x0ff7ba68 in start_thread (arg=0xbffffdd0) at pthread_create.c:313
>
> Is sched_setconfig_np() really the start routine given to
> pthread_create() in your application, I guess not. Or could this weird
> backtrace reveal a stack overflow?

Or maybe just too much frame information is optimized out, too 
aggressively. You may want to turn on debug symbols for building the 
Xenomai libraries, using --enable-debug.

-- 
Philippe.


  reply	other threads:[~2013-11-29  9:34 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 [this message]
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
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=52985FBF.8090608@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=norbert.bukuli@mediso.hu \
    --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.