From: Russell Johnson <russell.johnson@kratosdefense.com>
To: Philippe Gerum <rpm@xenomai.org>
Cc: "xenomai@lists.linux.dev" <xenomai@lists.linux.dev>
Subject: RE: [External] - Re: More details on health monitoring notifications
Date: Thu, 7 Jul 2022 19:25:47 +0000 [thread overview]
Message-ID: <PH1P110MB105066B5EF0817EFE24BF255E2839@PH1P110MB1050.NAMP110.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <87o7y2s1p9.fsf@xenomai.org>
[-- Attachment #1: Type: text/plain, Size: 830 bytes --]
Correct, it is running on x86. I am not sure what would be causing a page
fault in the EVL threads as I figured the mlockall call by evl_init would take
care of preventing that from happening.
I have tried to run the app with gdb (used to work fine pre-EVL), but now I
get all sorts off exceptions and error codes when trying to run in the
debugger. I quite frequently see EPERM issues with evl mutex unlock/lock (even
though it works fine when not run through a debugger). Also, when I swap the
thread mode flag from T_HMOBS to T_HMSIG and run in the debugger, I get a
"11776 CPU time limit exceeded (core dumped)" error on the create call for an
evl event in one of my threads. I am not sure why I am seeing such different
behavior in the debugger versus the normal run when it comes to the evl API
calls. Any ideas?
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 6759 bytes --]
prev parent reply other threads:[~2022-07-07 20:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 17:19 More details on health monitoring notifications Russell Johnson
2022-07-05 22:25 ` Russell Johnson
2022-07-06 14:57 ` Philippe Gerum
2022-07-06 19:05 ` Leonid Gasheev via Xenomai
2022-07-07 19:25 ` Russell Johnson [this message]
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=PH1P110MB105066B5EF0817EFE24BF255E2839@PH1P110MB1050.NAMP110.PROD.OUTLOOK.COM \
--to=russell.johnson@kratosdefense.com \
--cc=rpm@xenomai.org \
--cc=xenomai@lists.linux.dev \
/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.