From: Steve Freyder <steve@freyder.net>
To: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: --print-buffer-syncdelay, lib/cobalt/init.c:cobalt_help()
Date: Thu, 2 May 2019 11:37:52 -0500 [thread overview]
Message-ID: <5CCB1CE0.6020102@freyder.net> (raw)
Greetings,
I had a dev complain about losing stdio output in a Xenomai app, and
had never looked at rt_printf() and friends before. I had
problems attempting to use --print-buffer-syncdelay=1 to reduce the
delay to 1(ms), I found that my programs started complaining about an
invalid switch. Found that cobalt_help() was out of sync with the
actual switch name definition --print-sync-delay.
Here's a lame attempt at a patch.
Regards,
Steve
------------------------------------------------------------------------
lib/cobalt:
------------------------------------------------------------------------
diff -Naur a/init.c b/init.c
--- a/init.c 2018-06-15 10:26:19.692062099 -0500
+++ b/init.c 2019-05-02 11:16:07.894454047 -0500
@@ -349,7 +349,7 @@
fprintf(stderr, "--main-prio=<prio> main thread
priority\n");
fprintf(stderr, "--print-buffer-size=<bytes> size of a print
relay buffer (16k)\n");
fprintf(stderr, "--print-buffer-count=<num> number of print
relay buffers (4)\n");
- fprintf(stderr, "--print-buffer-syncdelay=<ms> max delay of
output synchronization (100 ms)\n");
+ fprintf(stderr, "--print-sync-delay=<ms> max delay of
output synchronization (100 ms)\n");
}
static struct setup_descriptor cobalt_interface = {
------------------------------------------------------------------------
next reply other threads:[~2019-05-02 16:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 16:37 Steve Freyder [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-11-15 23:26 --print-buffer-syncdelay, lib/cobalt/init.c:cobalt_help() 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=5CCB1CE0.6020102@freyder.net \
--to=steve@freyder.net \
--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.