From: Fabrice Gautier <Fabrice_Gautier@sdesigns.com>
To: 'Fernando Nasser' <fnasser@cygnus.com>
Cc: "GDB (E-mail)" <gdb@sourceware.cygnus.com>
Subject: RE: SIGINT handling for rdi target
Date: Thu, 27 Jul 2000 17:29:00 -0000 [thread overview]
Message-ID: <21DDE8E5343ED411840A00A0CC334020104801@EXCHANGE5_5> (raw)
> -----Original Message-----
> From: Fernando Nasser [ mailto:fnasser@cygnus.com ]
> Subject: Re: SIGINT handling for rdi target
>
>
> Fabrice Gautier wrote:
> >
> > Hi,
> >
> > 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
> >
> > Thank You
> >
>
> What is your host system? Linux? Solaris? Windows?
My host is WinNT + Cygwin.
> How old are your gdb sources? Are you using the command line
> interface?
I'm using the Insigth 5.0 release + patch for eCos.
If I use the Insight GUI, pressing the Stop button does nothing (in fact the
whole GUI seems frozen) Typing Ctrl+C in the console window of insight
doesn't help more.
BUT
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.
Thanks
A+
--
Fabrice Gautier
fabrice_gautier@sdesigns.com
next reply other threads:[~2000-07-27 17:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-27 17:29 Fabrice Gautier [this message]
2000-08-23 13:30 ` Grant Edwards
-- strict thread matches above, loose matches on Subject: below --
2000-07-27 16:40 Fabrice Gautier
2000-07-27 16:48 ` Fernando Nasser
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=21DDE8E5343ED411840A00A0CC334020104801@EXCHANGE5_5 \
--to=fabrice_gautier@sdesigns.com \
--cc=fnasser@cygnus.com \
--cc=gdb@sourceware.cygnus.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).