Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Denis PILAT <denis.pilat@st.com>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [RFC] Prints the frame id when target stops
Date: Wed, 17 Jan 2007 08:26:00 -0000	[thread overview]
Message-ID: <45ADDD77.8070505@st.com> (raw)
In-Reply-To: <17836.4836.53782.408349@kahikatea.snap.net.nz>

Nick Roberts wrote:
>  > Also it looks like you can't use ui_out_field_string as it prints CLI output
>  > also (when execeution stop, "info threads" etc).  Perhaps ui_out_field_stream
>  > does what you need.
>
> Or, more likely, wrap it in:
>
>       if (ui_out_is_mi_like_p (uiout))
>         {
>           ...
>         }
>
>   
You're right, my patch do much more printing than I expected.
I don't want to modify behavior of too much commands.

According to last discussion it seems to be hard to cache information 
returned by -stack-list-frame, may be we could print this frame id 
information
when the program stop only if stop reason is step or next.
Then it's up to the front end to be clever not refreshing the stack frame.

Denis


  reply	other threads:[~2007-01-17  8:26 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-15 16:21 Denis PILAT
2007-01-15 21:37 ` Nick Roberts
2007-01-15 23:11   ` Nick Roberts
2007-01-15 23:49     ` Nick Roberts
2007-01-17  8:26       ` Denis PILAT [this message]
2007-01-16 16:20 ` Vladimir Prus
2007-01-16 21:12   ` Nick Roberts
2007-01-16 23:38     ` Vladimir Prus
2007-01-17  6:18       ` Daniel Jacobowitz
2007-01-17 21:46         ` Vladimir Prus
2007-01-20 17:02           ` Daniel Jacobowitz
2007-01-17 21:29       ` Mark Kettenis
2007-01-17 21:38         ` Vladimir Prus
2007-01-17 21:59           ` Frédéric Riss
2007-01-17 22:14             ` Vladimir Prus
2007-01-18  8:00               ` Frederic RISS
2007-01-17 22:17             ` Daniel Jacobowitz
2007-01-18  7:58               ` Frederic RISS
2007-01-18 18:34                 ` Jim Blandy
2007-01-19 14:28                   ` Denis PILAT
2007-01-20 17:00                     ` Daniel Jacobowitz
2007-01-18 19:59                 ` Daniel Jacobowitz
2007-01-17  6:19     ` Daniel Jacobowitz
2007-01-18 21:13       ` Nick Roberts

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=45ADDD77.8070505@st.com \
    --to=denis.pilat@st.com \
    --cc=gdb-patches@sourceware.org \
    --cc=nickrob@snap.net.nz \
    /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