This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: gdb/mi and signals vs gdb/cli
- To: Mickael Gicquaire <Mickael dot Gicquaire at st dot com>
- Subject: Re: gdb/mi and signals vs gdb/cli
- From: Andrew Cagney <ac131313 at cygnus dot com>
- Date: Fri, 28 Sep 2001 19:48:17 -0400
- Cc: "gdb at sources dot redhat dot com" <gdb at sources dot redhat dot com>
- References: <1010928114759.ZM22692@bristol.st.com>
> 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