All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Drew <pythondrew@gmail.com>,
	Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: "Xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] gdb / threads on beaglebone black
Date: Wed, 28 May 2014 21:28:14 +0200	[thread overview]
Message-ID: <538638CE.6070306@xenomai.org> (raw)
In-Reply-To: <CAO0fa7as++VjLsRckoZ5XQ1nsfSwMvu3CUmQJVyr0PLyWjNntg@mail.gmail.com>

On 05/28/2014 09:19 PM, Drew wrote:
> On Wed, May 28, 2014 at 1:54 PM, Gilles Chanteperdrix <
> gilles.chanteperdrix@xenomai.org> wrote:
>
>>
>> Is there no message printed on the kernel console which would explain
>> why this syscall gets rejected?
>>
>
> A good idea! Unfortunately, after hooking up my debug serial cable I don't
> see any message when this happens. Running tail -f /var/log/messages
> doesn't show anything suspicious either. (well, it did find some things I
> didn't clean up in my main application... ;-)
>
> Grepping around for sys_barrier I come up with ksrc/nucleus/shadow.c. Does
> that contain the kernel side of the do while loop? I notice that
> xnshadow_sys_trace (which seems debugger related to me..) defaults its
> error to -ENOSYS...

It's not related to GDB, but to the internal tracing system available 
with CONFIG_IPIPE_TRACE. The call is likely dismissed even before 
Xenomai handles it. A brute force but straightforward way to get some 
hints would be to instrument the syscall router in the interrupt 
pipeline code.

-- 
Philippe.


  reply	other threads:[~2014-05-28 19:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-26  1:49 [Xenomai] gdb / threads on beaglebone black Drew
2014-05-26  7:09 ` Philippe Gerum
     [not found]   ` <CAO0fa7YQ0TxiAhbmFmt+41o+rugoLXKjXxtHygpthNOiu8gd9w@mail.gmail.com>
2014-05-26 13:23     ` Philippe Gerum
2014-05-27 12:05       ` Drew
2014-05-27 22:21         ` Drew
2014-05-28 14:08           ` Drew
2014-05-28 14:24             ` Philippe Gerum
2014-05-28 14:45               ` Michael Haberler
2014-05-28 17:54                 ` Gilles Chanteperdrix
2014-05-28 19:19                   ` Drew
2014-05-28 19:28                     ` Philippe Gerum [this message]
2014-05-28 20:06                     ` Gilles Chanteperdrix
2014-05-28 20:24                     ` Gilles Chanteperdrix
2014-05-28 20:31                   ` Michael Haberler
2014-05-28 20:36                     ` Philippe Gerum
2014-05-28 21:01                       ` Drew
2014-05-28 21:08                         ` Gilles Chanteperdrix
2014-05-28 22:27                           ` Gilles Chanteperdrix

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=538638CE.6070306@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=gilles.chanteperdrix@xenomai.org \
    --cc=pythondrew@gmail.com \
    --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.