This is the mail archive of the
insight@sources.redhat.com
mailing list for the Insight project.
RE: Ctrl-C interrupt
- To: "'insight at sources dot redhat dot com'" <insight at sources dot redhat dot com>
- Subject: RE: Ctrl-C interrupt
- From: Fabrice Gautier <Fabrice_Gautier at sdesigns dot com>
- Date: Tue, 14 Nov 2000 12:10:51 -0800
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
>
>