Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Bob Rossi <bob_rossi@cox.net>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] -stack-info-frame/-stack-list-frames
Date: Thu, 24 Apr 2008 01:45:00 -0000	[thread overview]
Message-ID: <18447.50648.436951.26648@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20080423230340.GA25265@brasko.net>

 > > If you want to know which frame the varobj is associated with GDB
 > > should supply some unique opaque identifier, and then the IDE can
 > > use that to show the frame number in a tooltip or wherever.
 > 
 > I've got a good idea, how about the frame number?

The frame number changes when a new frame is created, i.e., if the current
frame is used it's always "0", but it doesn't stay that way.

-- 
Nick                                           http://www.inet.net.nz/~nickrob


  reply	other threads:[~2008-04-23 23:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-23  5:33 Nick Roberts
2008-04-23  5:48 ` Vladimir Prus
2008-04-23  6:03   ` Nick Roberts
2008-04-23  6:16     ` Vladimir Prus
2008-04-23  9:50       ` Nick Roberts
2008-04-23 10:32         ` Vladimir Prus
2008-04-23 13:23           ` Nick Roberts
2008-04-23 13:44             ` Daniel Jacobowitz
2008-04-23 23:04               ` Nick Roberts
2008-04-23 23:27                 ` Daniel Jacobowitz
2008-04-24  0:40                   ` Bob Rossi
2008-04-24  1:45                     ` Nick Roberts [this message]
2008-04-24  1:31                   ` Nick Roberts
2008-04-24  1:48                     ` Nick Roberts
2008-04-24 10:24                     ` Daniel Jacobowitz
2008-04-25  1:48                       ` Nick Roberts
2008-04-25  2:03                         ` Daniel Jacobowitz
2008-04-25 11:41                           ` Nick Roberts
2008-04-23 13:53             ` Vladimir Prus
2008-04-23 23:23               ` 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=18447.50648.436951.26648@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=bob_rossi@cox.net \
    --cc=gdb-patches@sourceware.org \
    /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