From: Tom Tromey <tromey@redhat.com>
To: Keith Seitz <keiths@redhat.com>
Cc: "gdb-patches\@sourceware.org ml" <gdb-patches@sourceware.org>
Subject: Re: [RFA 1/2] Linespec rewrite (update 2)
Date: Fri, 30 Mar 2012 15:34:00 -0000 [thread overview]
Message-ID: <87obrertls.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4F74B583.6090008@redhat.com> (Keith Seitz's message of "Thu, 29 Mar 2012 12:18:27 -0700")
>>>>> "Keith" == Keith Seitz <keiths@redhat.com> writes:
Keith> I don't know. The whole comma thing is undocumented. The test suite
Keith> does contain list ranges. That's how I originally discovered
Keith> this. I've removed the list mode restriction, though, and it doesn't
Keith> affect test results at all.
You can write a test case using python that calls gdb.decode_line and
examines the remainder of the line.
Comma-termination isn't documented but I think it has to be preserved
anyway.
Keith> Yes, we can end up with a canonical form like "function:+5" or
Keith> "file:+5". The former is permitted (per recent maintainer request)
Keith> because we currently ignore the offset. [It is unprocessed in
Keith> convert_linespec_to_sals.] I'm not a fan of this,
What is the rationale for having a linespec where parts are ignored?
I couldn't think of a use for it. And, if current cvs rejects it, then
it seems like it is interfering with a useful future feature as well.
Tom> Why are minsyms sorted by pspace in one branch but not another?
Keith> No real good reason, other than that is the way it is done today. I
Keith> tried to keep the codepaths as similar as possible. I've merged the
Keith> two branches together. No need for minsyms to be singled out like
Keith> this.
Thanks. Keeping things the same is sufficient rationale, but now that
you've merged it, that is fine too.
Tom
next prev parent reply other threads:[~2012-03-30 15:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 23:18 Keith Seitz
2012-03-27 1:45 ` asmwarrior
2012-03-28 18:55 ` Tom Tromey
2012-03-27 13:56 ` Joel Brobecker
2012-03-27 14:31 ` Keith Seitz
2012-03-27 14:54 ` Joel Brobecker
2012-03-27 15:05 ` Joel Brobecker
2012-03-27 18:08 ` Keith Seitz
2012-03-28 20:46 ` Tom Tromey
2012-03-29 19:18 ` Keith Seitz
2012-03-30 15:34 ` Tom Tromey [this message]
2012-03-30 15:59 ` Keith Seitz
2012-03-30 16:37 ` Tom Tromey
2012-03-30 17:09 ` Joel Brobecker
2012-03-30 17:56 ` Tom Tromey
2012-03-30 18:05 ` Keith Seitz
2012-04-03 23:22 ` Keith Seitz
2012-04-05 15:22 ` Tom Tromey
2012-04-05 15:55 ` Doug Evans
2012-04-05 19:01 ` Keith Seitz
2012-07-22 19:33 ` Andreas Schwab
2012-07-23 17:57 ` Keith Seitz
2012-07-23 18:55 ` Tom Tromey
2012-07-23 21:13 ` Keith Seitz
2012-04-03 21:19 ` Doug Evans
2012-04-03 23:14 ` Keith Seitz
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=87obrertls.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@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