From: "Eli Zaretskii" <eliz@gnu.org>
To: gdb-patches@sources.redhat.com
Subject: Re: RFC: First stab at breakpoints in multiple locations
Date: Mon, 21 Mar 2005 19:48:00 -0000 [thread overview]
Message-ID: <01c52e4e$Blat.v2.4$97e63360@zahav.net.il> (raw)
In-Reply-To: <20050321142913.GA25191@nevyn.them.org> (message from Daniel Jacobowitz on Mon, 21 Mar 2005 09:29:13 -0500)
> Date: Mon, 21 Mar 2005 09:29:13 -0500
> From: Daniel Jacobowitz <drow@false.org>
> Cc: gdb-patches@sources.redhat.com
>
> 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.
Thanks for the explanations.
> You've successfully picked out the rawest part of the patch :-)
Well, all the rest were more or less mechanical changes, so these drew
my attention ;-)
prev parent reply other threads:[~2005-03-21 19:48 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
2005-03-21 19:48 ` Eli Zaretskii [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='01c52e4e$Blat.v2.4$97e63360@zahav.net.il' \
--to=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