From: Fernando Nasser <fnasser@cygnus.com>
To: Mark Salter <msalter@redhat.com>
Cc: Fabrice_Gautier@sdesigns.com, gdb@sources.redhat.com,
ecos-discuss@sourceware.cygnus.com
Subject: Re: Ctrl-C interrupt problem.
Date: Thu, 16 Nov 2000 05:48:00 -0000 [thread overview]
Message-ID: <3A13E574.5BF265BB@cygnus.com> (raw)
In-Reply-To: <200011161325.eAGDP8P09301@deneb.localdomain>
Nice catch Fabrice.
Congratulations on your persistence.
Fernando
Mark Salter wrote:
>
> >>>>> Fabrice Gautier writes:
>
> > [eCos and RedBoot guys, I think this may concern you
> > its about a ctrl-C problem which only happen when debugging via ethernet.
> > full story in the gdb list archives ]
>
> > I Got it!
> > Well, i hope....
>
> > And it make sens why it only happens with TCP...
>
> > The problem is that when gdb send the continue packet to the target, it wait
> > for the target to send the '+' Ack. During this time the SIGINT handler is
> > not set.
>
> > My guess is that RedBoot intedn to send it BUT (tata) the ethernet driver
> > just wait to have a full packet before really sending! So this happen when a
> > O packet is sent.
>
> > So i guess the only thing needed in RedBoot is to add a "flush" somewhere.
> > I'm not sure at what level, but i'll look at it tomorrow if nobody does it
> > before.
>
> > Thanks
>
> > --
> > Fabrice Gautier
> > fabrice_gautier@sdesigns.com
>
> Yes, it appears that redboot only flushes the output stream when
> it sees the end of a packet. This causes the problem you see.
>
> Look at .../redboot/current/src/net/net_io.c:net_io_putc().
>
> A quick workaround would be to also flush if a '+' is seen. This
> has a downside as it may severely impact download speeds, but at
> least it is functionally correct. YMMV.
>
> This needs to be fixed with a flush of the output stream prior
> to continuing or stepping the target. Its not clear to me right
> now how this can be done.
>
> --Mark
--
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:[~2000-11-16 5:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-15 20:46 Fabrice Gautier
2000-11-15 23:10 ` Fernando Nasser
2000-11-16 5:24 ` Mark Salter
2000-11-16 5:48 ` Fernando Nasser [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-15 17:48 Fabrice Gautier
2000-11-15 14:41 Fabrice Gautier
2000-11-14 20:19 Fabrice Gautier
2000-11-15 3:28 ` Eli Zaretskii
2000-11-15 12:48 ` Christopher Faylor
2000-11-14 16:39 Fabrice Gautier
2000-11-14 13:23 Fabrice Gautier
2000-11-10 16:13 Fabrice Gautier
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=3A13E574.5BF265BB@cygnus.com \
--to=fnasser@cygnus.com \
--cc=Fabrice_Gautier@sdesigns.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=gdb@sources.redhat.com \
--cc=msalter@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).