Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFC: First stab at breakpoints in multiple locations
Date: Mon, 21 Mar 2005 14:29:00 -0000	[thread overview]
Message-ID: <20050321142913.GA25191@nevyn.them.org> (raw)
In-Reply-To: <01c52dda$Blat.v2.4$0d3c4020@zahav.net.il>

On Mon, Mar 21, 2005 at 07:50:37AM +0200, Eli Zaretskii wrote:
> > Date: Sun, 13 Mar 2005 19:38:24 -0500
> > From: Daniel Jacobowitz <drow@false.org>
> > 
> > This patch (which, obviously, I'm not proposing to commit) is an initial
> > prototype of the one breakpoint, many locations idea I've discussed before.
> 
> Thanks (and sorry for the long response time).
> 
> These changes, and the general method you propose to resolve these
> issues, are fine with me, but could you please explain the reason to
> also change seemingly unrelated places like symtab.c and linespec.c?

Sure.  Half the linespec.c changes are unnecessary; they are left over
from an earlier prototype.  That's the build_one_canonical_line_spec
change.  The other changes to linespec.c and symtab.c provide an
interface to transform "file foo.c, line 12" into "file foo.c, line 12,
PC 0x8300; file foo.c, line 12, PC 0x9300" - i.e. resolving the line to
all of its PCs instead of just one.

You've successfully picked out the rawest part of the patch :-)  I
expect all that code to be rewritten in the next version, assuming I
find the time to go back to it.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-03-21 14:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-14  0:38 Daniel Jacobowitz
2005-03-21  5:54 ` Eli Zaretskii
2005-03-21 14:29   ` Daniel Jacobowitz [this message]
2005-03-21 19:48     ` Eli Zaretskii

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=20050321142913.GA25191@nevyn.them.org \
    --to=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sources.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