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: Andrew Cagney <ac131313 at cygnus dot com>
- Subject: Re: gdb/mi and signals vs gdb/cli
- From: Fernando Nasser <fnasser at redhat dot com>
- Date: Mon, 01 Oct 2001 10:36:26 -0400
- CC: Mickael Gicquaire <Mickael dot Gicquaire at st dot com>, "gdb at sources dot redhat dot com" <gdb at sources dot redhat dot com>
- Organization: Red Hat Canada
- References: <1010928114759.ZM22692@bristol.st.com> <3BB50C41.10807@cygnus.com>
Andrew Cagney wrote:
>
> > 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,
I am afraid we may be missing a ui_out_flush() at the end of all
of the switch clauses in infrun.c
Fernando
--
Fernando Nasser
Red Hat Canada Ltd. E-Mail: fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9