From: Fernando Nasser <fnasser@redhat.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: [ser-unix.c] Fix handling of baud rates
Date: Thu, 26 Apr 2001 07:47:00 -0000 [thread overview]
Message-ID: <3AE83490.6F92F95A@redhat.com> (raw)
In-Reply-To: <1659-Thu26Apr2001173526+0300-eliz@is.elta.co.il>
Eli Zaretskii wrote:
>
> > Date: Thu, 26 Apr 2001 10:15:15 -0400
> > From: Fernando Nasser <fnasser@redhat.com>
> >
> > The problem with the error message is that:
> > 1) there is nothing very nice to set the errno to (suggestions?)
>
> EINVAL comes to mind, although it is admittedly not very specific.
>
Yes, but it is good enough if we show the warning first. Thank you.
> > But as we are adding a warning(), why not just say:
> > "Illegal baud rate %d; using %d instead."
>
> Can you prompt for another value (after making sure this is an
> interactive session)?
>
We already prompt for many things, but I believe we want to get rid of
these prompts outside the interpreters. It complicates the
interpreter<->libgdb protocol, I've heard. The idea is that idempotent
libgdb operations fail and the interpreter (after asking the user what
to do) retries them with the proper values.
> (Btw, saying ``illegal'' is discouraged by the GNU standards, unless
> you are talking about actions that break the law. ``Invalid'' is the
> suggested alternative.)
Thanks, I didn't know that. Please read is as "invalid".
I just though of another problem with the fall back: most of the boards
do no accept connection at different speeds and GDB current has a very
annoying behavior of keep trying these impossible connections for ages.
If it would quickly realize that the communication is not good and give
up this would be a good thing. Actually, I have many requests from
users that want GDB to stop being so stubborn. But until that is fixed,
we may end up getting into that trap. So, we would have to go with the
error solution until that is fixed.
Is that right?
--
Fernando Nasser
Red Hat Canada Ltd. E-Mail: fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9
next prev parent reply other threads:[~2001-04-26 7:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-25 15:39 Fernando Nasser
2001-04-26 0:29 ` Eli Zaretskii
2001-04-26 7:17 ` Fernando Nasser
[not found] ` <1659-Thu26Apr2001173526+0300-eliz@is.elta.co.il>
2001-04-26 7:47 ` Fernando Nasser [this message]
2001-04-26 9:44 ` Eli Zaretskii
2001-05-10 12:08 ` RFA: [ser-unix.c] Fix handling of baud rates [REPOST] Fernando Nasser
2001-05-11 1:17 ` Eli Zaretskii
2001-05-11 11:31 ` Fernando Nasser
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=3AE83490.6F92F95A@redhat.com \
--to=fnasser@redhat.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox