From: Mickael Gicquaire <Mickael.Gicquaire@st.com>
To: ac131313@cygnus.com <ac131313@cygnus.com>
Cc: gdb@sources.redhat.com
Subject: Re: gdb/mi and signals vs gdb/cli
Date: Mon, 01 Oct 2001 02:03:00 -0000 [thread overview]
Message-ID: <1011001100039.ZM26860@bristol.st.com> (raw)
hi all ,
>
> How recent a GDB? It sounds like it lost the signal -> bug.
>
> Andrew
>
The version of the gdb that i am using is :
GNU gdb 20010628 (MI_OUT)
This GDB was configured as "--host=sparc-sun-solaris2.8
--target=sh-superh-elf".
I am going to download a newer version to see if it 's due to that version of
gdb.
Otherwise.., any other suggestions ?
cheers Mickael.
> > hi all !
> > i have a question concerning gdb/mi interface and signals handling.
> > The SIGTERM signal send by my remote target does not appear when
> > i use gdb with its mi interface.
> >
> > The program runs to completion and the *stopped is displayed.
> >
> > -exec-continue
> > ^running
> > (gdb)
> > *stopped
> > (gdb)
> >
> > whereas if i used Gdb with the cli interface i get
> > (top-gdb) c
> > Continuing.
> > Program received signal SIGTERM, Terminated.
> > 0xac009bae in ?? ()
> >
> > Does someone knows what is happening to my SIGTERM signal ??
>
>
> How recent a GDB? It sounds like it lost the signal -> bug.
>
> Andrew
>
>
>
--
---------------------------------------------------------------------------
| Mickael Gicquaire | email mickael.gicquaire@.st.com | |
| | | _____________ |
| STMicroelectronics | | / ___/__ __/ |
| 1000 Aztec West | | \__ \ / / |
| Almondsbury | Phone 01454-462342 | /____/ /__/ |
| BRISTOL | | |
---------------------------------------------------------------------------
next reply other threads:[~2001-10-01 2:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-01 2:03 Mickael Gicquaire [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-01 9:07 Mickael Gicquaire
2001-09-28 3:48 Mickael Gicquaire
2001-09-28 16:48 ` Andrew Cagney
2001-10-01 7:43 ` Fernando Nasser
2001-10-01 8:26 ` Andrew Cagney
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=1011001100039.ZM26860@bristol.st.com \
--to=mickael.gicquaire@st.com \
--cc=ac131313@cygnus.com \
--cc=gdb@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