From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@redhat.com>
Cc: pedro@codesourcery.com, gdb-patches@sourceware.org, sergiodj@redhat.com
Subject: Re: [PATCH 2/6] Introduce `pre_expanded sals'
Date: Wed, 13 Apr 2011 09:51:00 -0000 [thread overview]
Message-ID: <E1Q9wjM-0005tS-IO@fencepost.gnu.org> (raw)
In-Reply-To: <m3y63f2p3b.fsf@fleche.redhat.com> (message from Tom Tromey on Tue, 12 Apr 2011 14:26:32 -0600)
> From: Tom Tromey <tromey@redhat.com>
> Cc: gdb-patches@sourceware.org, Sergio Durigan Junior <sergiodj@redhat.com>
> Date: Tue, 12 Apr 2011 14:26:32 -0600
>
> Furthermore, I think the `probe:' prefix should let us lift this
> restriction anyhow. It is a way of saying "this is not an ordinary
> source location, but something else".
If so, perhaps we shouldn't consider them locations at all, but rather
symbolic names of a set of locations.
> I'd rather change gdb to set a breakpoint at all matching locations, and
> let the user disambiguate if that is really what he wanted.
How would she disambiguate that?
Anyway, these issues were discussed at length in the past (with your
suggestion being on the table, as well as others), so perhaps we all
should re-read that before reiterating the same arguments again.
next prev parent reply other threads:[~2011-04-13 9:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 3:08 Sergio Durigan Junior
2011-04-06 20:13 ` Tom Tromey
2011-04-12 11:18 ` Pedro Alves
2011-04-12 11:53 ` Jan Kratochvil
2011-04-12 13:30 ` Pedro Alves
2011-04-12 20:34 ` Tom Tromey
2011-04-12 22:22 ` Matt Rice
2011-04-13 9:53 ` Eli Zaretskii
2011-07-27 17:08 ` Tom Tromey
2011-07-29 20:36 ` Sergio Durigan Junior
2011-08-04 20:41 ` Tom Tromey
2011-08-05 3:41 ` Sergio Durigan Junior
2011-08-05 14:40 ` Tom Tromey
2011-08-05 18:06 ` Sergio Durigan Junior
2011-08-10 14:24 ` Tom Tromey
2011-05-03 16:09 ` Jerome Guitton
2011-05-03 18:17 ` Joel Brobecker
2011-04-12 20:26 ` Tom Tromey
2011-04-13 9:51 ` Eli Zaretskii [this message]
2011-04-13 19:20 ` Tom Tromey
2011-04-15 10:37 ` Eli Zaretskii
2011-04-18 18:37 ` Pedro Alves
2011-04-27 18:02 ` Jan Kratochvil
2011-04-29 20:42 ` Tom Tromey
2011-04-11 21:08 ` Jan Kratochvil
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=E1Q9wjM-0005tS-IO@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=sergiodj@redhat.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