From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: fnasser@redhat.com
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: [ser-unix.c] Fix handling of baud rates
Date: Thu, 26 Apr 2001 09:44:00 -0000 [thread overview]
Message-ID: <6480-Thu26Apr2001194506+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <3AE83490.6F92F95A@redhat.com>
> Date: Thu, 26 Apr 2001 10:45:36 -0400
> From: Fernando Nasser <fnasser@redhat.com>
>
> > > 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.
Yes, that makes sense. Is there any way that libgdb can give the
interpreter an indication that it wants to prompt the user?
> So, we would have to go with the error solution until that is fixed.
>
> Is that right?
I'm not very experienced with debugging such boards, but it sounds
that a failure would indeed be the best way out.
next prev parent reply other threads:[~2001-04-26 9:44 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
2001-04-26 9:44 ` Eli Zaretskii [this message]
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=6480-Thu26Apr2001194506+0300-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=fnasser@redhat.com \
--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