From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: rpm@xenomai.org, xenomai@xenomai.org
Subject: Re: [Xenomai-core] [BUG] oops on skincall without nucleus being loaded
Date: Fri, 23 Jun 2006 20:22:58 +0200 [thread overview]
Message-ID: <17564.12674.330717.263818@domain.hid> (raw)
In-Reply-To: <17564.11393.93645.251930@domain.hid>
Gilles Chanteperdrix wrote:
> misinterpretation. When issuing syscalls with a fixed muxid whereas
> there is no interface corresponding to this muxid, the nucleus crashes,
> but it is acceptable, user-space interfaces should issue an
> __xn_sys_bind syscall first.
This is not even possible, since the invalid syscall go through
do_hisyscall_event first and get handled there.
--
Gilles Chanteperdrix.
next prev parent reply other threads:[~2006-06-23 18:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 10:35 [Xenomai-core] [BUG] oops on skincall without nucleus being loaded Jan Kiszka
2006-06-22 10:50 ` Jan Kiszka
2006-06-23 13:41 ` Gilles Chanteperdrix
2006-06-23 16:26 ` Philippe Gerum
2006-06-23 18:01 ` Gilles Chanteperdrix
2006-06-23 18:22 ` Gilles Chanteperdrix [this message]
2006-06-27 8:06 ` Jan Kiszka
2006-06-27 11:29 ` Gilles Chanteperdrix
2006-06-23 14:34 ` 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=17564.12674.330717.263818@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=rpm@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.