Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: Stan Shebs <stan@codesourcery.com>
Cc: Michael Snyder <msnyder@vmware.com>,
	 "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	 "tromey@redhat.com" <tromey@redhat.com>
Subject: Re: PR8554: New command to save breakpoints to a file
Date: Thu, 15 Apr 2010 19:10:00 -0000	[thread overview]
Message-ID: <201004152010.14338.pedro@codesourcery.com> (raw)
In-Reply-To: <4BC76205.1040303@codesourcery.com>

On Thursday 15 April 2010 19:59:17, Stan Shebs wrote:
> I can't remember if we've discussed this idea before, but a simple way 
> to handle in the future might be simply to introduce a syntax for 
> referring to specific locals - function:::local, file:line:::local, for 
> instance.  You get a sal that maps to a block, then can find the block's 
> symbol with that name.  If the name also occurs in superblocks, you 
> could make a policy decision as to whether to include the first found, 
> or all found.

Dunno.  Maybe we've read it over in HPDF's parallel debugger's "standard",
or a PR or something.  Maybe Frysk implemented it?  It's certainly not
a novel idea.  ;-)

Anyway, that handles the symbol scoping, not the fact that to set
a watchpoint, the frame where the local is defined needs to be 
active, otherwise, you can't read the initial value for
comparision and change detection.  Certainly more would have
to be changed to make it work.

I certainly think that the feature is quite useful even
with the locals caveat.

-- 
Pedro Alves


      reply	other threads:[~2010-04-15 19:10 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-09  2:41 Pedro Alves
2010-04-09 16:17 ` Tom Tromey
2010-04-09 17:23   ` Pedro Alves
2010-04-10  4:10     ` Sergio Durigan Junior
2010-04-12 18:15     ` Pedro Alves
2010-04-15 17:52       ` Michael Snyder
2010-04-15 18:27         ` Pedro Alves
2010-04-15 18:46           ` Michael Snyder
2010-04-15 18:53             ` Pedro Alves
2010-04-15 18:58               ` Michael Snyder
2010-04-15 19:58                 ` Pedro Alves
2010-04-15 22:49                   ` Michael Snyder
2010-04-15 22:52                     ` Michael Snyder
2010-04-15 22:58                       ` Michael Snyder
2010-04-15 23:05                         ` Pedro Alves
2010-04-15 23:15                           ` Michael Snyder
2010-04-15 23:25                             ` Pedro Alves
2010-05-05  8:28                               ` Hui Zhu
2010-04-15 23:14                         ` Michael Snyder
2010-04-15 23:20                           ` Pedro Alves
2010-04-15 23:01                     ` Pedro Alves
2010-04-15 18:59           ` Stan Shebs
2010-04-15 19:10             ` Pedro Alves [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=201004152010.14338.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.com \
    --cc=stan@codesourcery.com \
    --cc=tromey@redhat.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