From: Eli Zaretskii <eliz@gnu.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [9/9] expand locations
Date: Sat, 08 Sep 2007 11:50:00 -0000 [thread overview]
Message-ID: <uzlzxqsu7.fsf@gnu.org> (raw)
In-Reply-To: <200709080313.33625.vladimir@codesourcery.com> (message from Vladimir Prus on Sat, 8 Sep 2007 03:13:33 +0400)
> From: Vladimir Prus <vladimir@codesourcery.com>
> Date: Sat, 8 Sep 2007 03:13:33 +0400
>
> + One case I'm not sure about is where originally we've
> + set breakpoint at file:line. There were several PC values
> + for that file:line, due to optimization, all in one block.
> + We've picked on PC value. If "clear" is issued with another
> + PC corresponding to the same file:line, what should we do? */
I think we should ask the user what she meant.
next prev parent reply other threads:[~2007-09-08 11:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-07 23:14 Vladimir Prus
2007-09-08 0:21 ` Pedro Alves
2007-09-08 1:41 ` Jim Blandy
2007-09-08 3:42 ` Daniel Jacobowitz
2007-09-08 11:50 ` Eli Zaretskii [this message]
2007-09-23 8:22 ` Vladimir Prus
2007-09-23 19:23 ` 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=uzlzxqsu7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=vladimir@codesourcery.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