From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Michael Walle <michael@walle.cc>
Subject: Re: [PATCH] remote target interrupt before ack
Date: Tue, 05 Apr 2011 16:10:00 -0000 [thread overview]
Message-ID: <201104051710.10938.pedro@codesourcery.com> (raw)
In-Reply-To: <201104042238.32058.michael@walle.cc>
On Monday 04 April 2011 21:38:32, Michael Walle wrote:
> Am Montag 04 April 2011, 22:21:21 schrieb Pedro Alves:
> > On Monday 04 April 2011 21:00:15, Michael Walle wrote:
> > > the following patch puts the sending of the interrupt/break sequence
> > > before the proforma ACK. This guarantees the ACK won't be delivered to
> > > an application on the remote side.
>
> >
> > Can you explain what the latter sentence means a bit better?
> >
> Oh, i forgot to mention that this bug affects serial lines which are shared
> with the GDB stub. Assume the remote needs a BREAK to start its gdb stub. If
> you send the '+' before the BREAK it will be delivered to the actual
> application running on the device (and of course listening on the serial
> port). [If there happens to be some echo service things will even go worse,
> because the echoed '+' will be interpreted by GDB as an ACK to the first sent
> packet.]
Okay, makes sense. I figured it was something like that, but doesn't hurt
to be explicit so we don't have to guess, and for the benefit of
the archives.
Patch is okay, thanks.
--
Pedro Alves
next prev parent reply other threads:[~2011-04-05 16:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 20:00 Michael Walle
2011-04-04 20:21 ` Pedro Alves
2011-04-04 20:38 ` Michael Walle
2011-04-05 16:10 ` Pedro Alves [this message]
2011-04-26 11:01 ` Michael Walle
2011-04-26 15:40 ` Tom Tromey
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=201104051710.10938.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=michael@walle.cc \
/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