Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Elena Zannoni <ezannoni@cygnus.com>
Cc: Keith Seitz <keiths@cygnus.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Add missing "reason" to print_stop_reason
Date: Wed, 11 Jul 2001 09:41:00 -0000	[thread overview]
Message-ID: <3B4C81A2.90207@cygnus.com> (raw)
In-Reply-To: <15180.32973.225364.383767@krustylu.cygnus.com>

> I don't have power to approve this because I don't maintain infrun.c,
> but since I wrote print_stop_reason, I recommend the patch for approval. 


I think it is pretty obvious (yes, ok).

	Andrew


> Keith Seitz writes:
>  > Hi,
>  > > Okay, I know that this is all due for some massaging, but this patch will
>  > allow the workaround to work a little better until the formal mechanism is
>  > in place.
>  > > Keith
>  > > ChangeLog:
>  > 2001-07-11  Keith Seitz  <keiths@redhat.com>
>> > * infrun.c (print_stop_reason): Add missing uiout field
>  > "reason" for SIGNAL_RECEIVED case.
>  > > Patch:
>  > Index: infrun.c
>  > ===================================================================
>  > RCS file: /cvs/src/src/gdb/infrun.c,v
>  > retrieving revision 1.42
>  > diff -u -p -r1.42 infrun.c
>  > --- infrun.c	2001/07/06 03:53:11	1.42
>  > +++ infrun.c	2001/07/11 15:14:25
>  > @@ -3382,6 +3382,8 @@ print_stop_reason (enum inferior_stop_re
>  > annotate_signal ();
>  > ui_out_text (uiout, "\nProgram received signal ");
>  > annotate_signal_name ();
>  > +      if (ui_out_is_mi_like_p (uiout))
>  > +	ui_out_field_string (uiout, "reason", "signal-received");
>  > ui_out_field_string (uiout, "signal-name", target_signal_to_name (stop_info));
>  > annotate_signal_name_end ();
>  > ui_out_text (uiout, ", ");
>  > 
> 



      reply	other threads:[~2001-07-11  9:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-11  8:16 Keith Seitz
2001-07-11  9:30 ` Elena Zannoni
2001-07-11  9:41   ` Andrew Cagney [this message]

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=3B4C81A2.90207@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=ezannoni@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=keiths@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