From: Joel Brobecker <brobecker@adacore.com>
To: Keith Seitz <keiths@redhat.com>
Cc: archer@sourceware.org
Subject: Re: Stop the Insanity! Linespec Rewrite
Date: Thu, 08 Mar 2012 03:02:00 -0000 [thread overview]
Message-ID: <20120308030202.GD2867@adacore.com> (raw)
In-Reply-To: <4F57CEF1.50001@redhat.com>
> Actually it was a failure on the new parser to properly deal with
> parse_to_comma_and_eval (used in linespec_expression_to_pc), which
> retokenizes the input based on whitespace.
Our emails crossed paths :-)
> Could you verify that I didn't break anything else?
Of course. You've got to love git and the fact that you're making
fast-forward pushes (instead of rebasing + forced push), which
hugely simplifies my task.
Anyway, all this rambling to say that the testsuite runs clean.
I also forgot to say that your patch improves the diagnostic
in the following case:
--- Regression: KB27-008__file_star_line_linespec:break foo.adb:*:3
- Could not match y-or-n question
Function "*:3" not defined in "foo.adb".
Make breakpoint pending on future shared library load
- Against input line
Function "*" not defined in "foo.adb".
Make breakpoint pending on future shared library load
The difference is that is says function "*" instead of "*:3" when
doing:
(gdb) break foo.adb:*:3
For the record, "*" used to be a way in AdaCore's debugger to say
"break on all instances". It was a long long time ago, and Paul and
I killed that syntax since then, and we have a check to verify
that it returns an error.
I wonder if it would work with an operator, though... I think you'd
need the double-quotes. Aha!
(gdb) b ops.adb:"*":35
Breakpoint 1 at 0x40217a: file /[...]/ops.adb, line 35.
(gdb) b ops.adb:*:35
Function "*:35" not defined in "ops.adb".
Make breakpoint pending on future shared library load? (y or [n]) n
And your debugger behaves beautifully as well:
(gdb) b ops.adb:"*":35
Breakpoint 1 at 0x40217a: file /[...]/ops.adb, line 35.
(gdb) b ops.adb:*:35
Function "*" not defined in "ops.adb".
Make breakpoint pending on future shared library load? (y or [n]) n
(this is using the gdb.ada/operator_bp testcase).
I need to augment that testcase, now :-/.
--
Joel
prev parent reply other threads:[~2012-03-08 3:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-02 1:14 Keith Seitz
2012-03-02 17:00 ` Tom Tromey
2012-03-02 22:41 ` Keith Seitz
2012-03-03 2:36 ` Tom Tromey
2012-03-02 19:07 ` [Archer] " Joel Brobecker
2012-03-02 22:49 ` Keith Seitz
2012-03-06 17:40 ` [Archer] " Joel Brobecker
2012-03-06 19:08 ` Keith Seitz
2012-03-06 19:36 ` Keith Seitz
2012-03-06 21:50 ` [Archer] " Joel Brobecker
2012-03-07 0:11 ` [Archer] " Joel Brobecker
2012-03-07 1:08 ` Keith Seitz
2012-03-07 1:26 ` [Archer] " Joel Brobecker
2012-03-07 14:39 ` Tom Tromey
2012-03-07 15:01 ` Tom Tromey
2012-03-07 15:39 ` [Archer] " Joel Brobecker
2012-03-07 16:06 ` Tom Tromey
2012-03-07 21:19 ` Joel Brobecker
2012-03-07 21:11 ` [Archer] " Keith Seitz
2012-03-08 3:02 ` Joel Brobecker [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=20120308030202.GD2867@adacore.com \
--to=brobecker@adacore.com \
--cc=archer@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).