Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Frederic RISS <frederic.riss@st.com>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: "Frédéric Riss" <frederic.riss@gmail.com>,
	gdb-patches@sources.redhat.com
Subject: Re: [RFC] Prints the frame id when target stops
Date: Thu, 18 Jan 2007 08:00:00 -0000	[thread overview]
Message-ID: <1169107204.3288.130.camel@localhost.localdomain> (raw)
In-Reply-To: <200701180114.20338.ghost@cs.msu.su>

On Thu, 2007-01-18 at 01:14 +0300, Vladimir Prus wrote:
> On Thursday 18 January 2007 00:59, Frédéric Riss wrote:
> > If you just want to cache the result of -stack-list-frames, then you'd
> > have to edit out the addr field which contains the frame's PC for the
> > top frame... not very nice.
> 
> Or introduce 'struct cached_result_of_stack_list_frames' that
> can contain whatever I like and which can be conveniently edited.
> 
> You've actually pointed a nice problem -- if frontend avoid -stack-list-frames
> when frame id did not change, it will have stale address of the top frame too.

Well, the frontend might not care about the exact PC (which it'll get
anyway in the stop reason? can't remember), or it can request only the
top frame which is basically free.

Fred.


  reply	other threads:[~2007-01-18  8:00 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
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 [this message]
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=1169107204.3288.130.camel@localhost.localdomain \
    --to=frederic.riss@st.com \
    --cc=frederic.riss@gmail.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=ghost@cs.msu.su \
    /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