From: Jeff Webb <jeff.webb@domain.hid>
To: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Xenomai v2.2.3
Date: Wed, 20 Sep 2006 15:02:48 -0500 [thread overview]
Message-ID: <45119E68.9050608@domain.hid> (raw)
In-Reply-To: <1158777216.5043.46.camel@domain.hid>
Philippe Gerum wrote:
> Ok, that helps thanks. Now, running the latency test over GDB instead of
> using the "run" script would likely give us a backtrace for the
> segfault. I'd be interested to know where the latency application is
> sent the fault signal. E.g.
>
> modprobe xeno_nucleus
> modprobe xeno_native
> (if needed)
>
> then,
>
> cd /usr/xenomai/testsuite/latency
> gdb latency
> r
> ...(SIGSEGV)...
> bt
If I just run latency, I get the segfault:
[root@domain.hid webb-ja]# cd /usr/xenomai/testsuite/latency/
[root@domain.hid latency]# /sbin/modprobe xeno_native
[root@domain.hid latency]# ./latency
== Sampling period: 100 us
== Test mode: periodic user-mode task
== All results in microseconds
Segmentation fault
If I try to run gdb on it, it just hangs when I type the "r" command:
[root@domain.hid webb-ja]# cd /usr/xenomai/testsuite/latency/
[root@domain.hid latency]# /sbin/modprobe xeno_native
[root@domain.hid latency]# gdb latency
GNU gdb Red Hat Linux (5.3.90-0.20030710.41rh)
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-redhat-linux-gnu"...
(no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1".
(gdb) r
Starting program: /usr/xenomai-2.2.3/testsuite/latency/latency
(no debugging symbols found)...[Thread debugging using libthread_db enabled]
Error while reading shared library symbols:
Cannot find new threads: generic error
(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
At this point, the terminal is locked, and I have to use kill -9 from another terminal. I did some googling on the error message and found this thread:
http://sources.redhat.com/ml/gdb/2005-04/msg00201.html
Any hints on what I am doing wrong? Sorry, if I am doing something silly and don't realize it.
Thanks,
Jeff
next prev parent reply other threads:[~2006-09-20 20:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-18 7:28 [Xenomai-core] Xenomai v2.2.3 Philippe Gerum
2006-09-18 21:58 ` [Xenomai-help] " Jeff Webb
2006-09-19 22:01 ` Jeff Webb
2006-09-20 9:24 ` Philippe Gerum
2006-09-20 14:44 ` Jeff Webb
2006-09-20 15:22 ` Philippe Gerum
2006-09-20 16:14 ` Philippe Gerum
2006-09-20 18:24 ` Jeff Webb
2006-09-20 18:33 ` Philippe Gerum
2006-09-20 20:02 ` Jeff Webb [this message]
2006-09-20 20:19 ` Jeff Webb
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=45119E68.9050608@domain.hid \
--to=jeff.webb@domain.hid \
--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.