From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: xenomai@xenomai.org
Subject: [Xenomai-help] Problem trying to find secondary mode switches.
Date: Fri, 01 Jun 2007 11:07:33 +0200 [thread overview]
Message-ID: <465FE1D5.6070906@domain.hid> (raw)
Hi,
I am using the XNTRAPSW option to try and find secondary mode switches
in some piece of code for which I do not have the sources. I have
installed the usual signal handler which dumps the backtrace, just as in
ksrc/skins/native/snippet/sigxcpu.c. But the problem is that the
backtrace is not helpful, it show addresses in libpthread and
libpthread_rt global destructor sections.
By adding some printks in shadow.c I know that what causes the mode
switch is the linux arm syscall 78 aka gettimeofday.
So, my question is: is there any chance that the signal sent by send_sig
in xnshadow_relax could be received by another thread than send_sig
target ? If not, where should I look for the reason of this wrong
backtrace ?
--
Gilles Chanteperdrix
next reply other threads:[~2007-06-01 9:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 9:07 Gilles Chanteperdrix [this message]
2007-06-01 9:43 ` [Xenomai-help] Problem trying to find secondary mode switches Dmitry Adamushko
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=465FE1D5.6070906@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--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.