This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: SIGINT handling for rdi target
- To: Fabrice Gautier <Fabrice_Gautier at sdesigns dot com>
- Subject: Re: SIGINT handling for rdi target
- From: Grant Edwards <grante at visi dot com>
- Date: Wed, 23 Aug 2000 15:30:35 -0500
- Cc: "'Fernando Nasser'" <fnasser at cygnus dot com>,"GDB (E-mail)" <gdb at sourceware dot cygnus dot com>
- References: <21DDE8E5343ED411840A00A0CC334020104801@EXCHANGE5_5>
On Thu, Jul 27, 2000 at 05:28:03PM -0700, Fabrice Gautier wrote:
> > > I'm using a EmbededICE device with an ARM board and I connect
> > > using the RDI target. The problem is that there I can't
> > > interrupt the target from gdb. Looking in the code, I didn't
> > > saw any SIGINT handling in remote-rdi.c as there is remote.c
> > > for the serial target.
> > >
> > > Does anyone know why? And If this is related to my problem
> >
> > What is your host system? Linux? Solaris? Windows?
>
> My host is WinNT + Cygwin.
[...]
> When launching only the cmd line interface (gdb -nw) ctrl+c works.
> AND
> With the GUI interface, sending an explicit sigint to the process (kill
> -sigint pid) works as it should. With the message RDI_execute: you pressed
> Escape.
>
> So it seems this is only a problem with the GUI.
I've run into this also. I can do a "kill -INT" on the gdb
process. This stops the remote, and then the Insight GUI pops
up a dialog box complaining about getting a signal. When I
acknowlege the dialog box, the GUI then just locks up.
Anybody figure out how to get this to work?
--
Grant Edwards
grante@visi.com