From: Fabrice Gautier <Fabrice_Gautier@sdesigns.com>
To: "'insight@sources.redhat.com'" <insight@sources.redhat.com>
Subject: RE: Ctrl-C interrupt
Date: Tue, 14 Nov 2000 12:12:00 -0000 [thread overview]
Message-ID: <B1F6452C89AFD411AE0800A0CC734C23015012@EMAIL1> (raw)
Hi,
Nobody has some "insight" about that ?
Thanks.
> -----Original Message-----
> From: Fabrice Gautier [ mailto:Fabrice_Gautier@sdesigns.com ]
> Sent: Friday, November 10, 2000 5:39 PM
> To: 'insight@sources.redhat.com'
> Subject: Ctrl-C interrupt
>
>
> Hi,
>
> I'm using gdb (insight) to debug an eCos program running
> above RedBoot. I
> have a problem when running some test program to make the ctrl-C works
> correctly. The target is a remote i386 PC.
>
> My program only do some printf (which are sent to gdb as O
> packets) in a
> loop wiht some delay betwen the printfs.
>
> What happenif that I can interrupt with Ctrl-C a first time, then if I
> continue Ctrl-C doesn't work again immediately, i have to
> wait for another
> printf (and so a O packet) in order to be abble to use ctrl-C again.
>
> This happen only when using Ethernet not when debugging
> through serial port.
>
> I first thought it was a problem with the gdb stub in
> RedBoot/eCos. But
> when I "set remote debug 1" i can see that the first time i
> hit ctrl-C i
> have:
>
> remote_interrupt called
> remote_stop called
>
> but the second time (when it doesn't works) i have nothing.
> So it looked
> like the SIGINT didn't reach the correct gdb function somewhere.
>
>
> I have been looking a bit in the gdb code to figure out what
> was the path
> when receving a ctrl-C, but i'm not sure which function
> exaclty is called.
> remote_interrupt or async_remote_interrupt (which) seems to
> be called when
> it works, but i've also seen some SIGINT handling with
> handle_remote_sigint
> or request_quit.
>
> Okay,
> All of the above, i've already sent to the gdb list, but i
> figured out that
> with the insight STOP button i've somthing a bit different:
>
> When I press the button nothing happen until something is
> printf'ed then the
> SIGINT is received. When i only use the command line, the
> SIGINT is never
> caught if i don't retype ctrl-C after the printf.
>
> I suspect this may have something to do - in part - with terminals.
>
> Plus, what i forgot to says previously was that it is the
> cygwin version of
> gdb-insight that I use. The cygwin console may be different
> than the usual
> unix/linux consoles.
>
> Thanks
>
> --
> Fabrice Gautier
> fabrice_gautier@sdesigns.com
>
>
next reply other threads:[~2000-11-14 12:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-14 12:12 Fabrice Gautier [this message]
2000-11-14 12:36 ` Fernando Nasser
-- strict thread matches above, loose matches on Subject: below --
2000-11-10 17:40 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=B1F6452C89AFD411AE0800A0CC734C23015012@EMAIL1 \
--to=fabrice_gautier@sdesigns.com \
--cc=insight@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).