From: Joel Brobecker <brobecker@adacore.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: Tue, 27 Mar 2012 13:56:00 -0000 [thread overview]
Message-ID: <20120327135623.GC2701@adacore.com> (raw)
In-Reply-To: <4F70F8F7.503@redhat.com>
Hi Keith,
I tested your patch locally, and unfortunately, it regresses in
the following situation:
(gdb) break ops.adb:"+":10
FUNCTION:OFFSET is unimplemented
It seems to be doing it for all operators, for instance:
(gdb) break ops.adb:"/":25
FUNCTION:OFFSET is unimplemented
It's a series of tests I meant to add after you check in your patch,
because I believe the output changes (that's something we were
discussing on Archer). Perhaps it would be better if I wrote a patch
to be applied after we apply yours. That way, you can include it
in your tree and immediately notice this regression...
I'll probably have some time to look at this this afternoon, if you're
tied up.
Git also notices the following little details when applying your
patch:
> /home/brobecke/linespec-rewrite-parser-2.patch:810: trailing whitespace.
> /* Throw an appropriate error when an unexpected token is encountered
> /home/brobecke/linespec-rewrite-parser-2.patch:3180: trailing whitespace.
> /home/brobecke/linespec-rewrite-parser-2.patch:3960: trailing whitespace.
> {
> /home/brobecke/linespec-rewrite-parser-2.patch:4106: trailing whitespace.
> add the_tests "$srcfile:main:$x" invalid_label [string trim $x] "main"
> /home/brobecke/linespec-rewrite-parser-2.patch:4246: trailing whitespace.
> return f.baz (foo::bar () + 3);
> warning: squelched 1 whitespace error
> warning: 6 lines add whitespace errors.
Not terribly important, but easy to fix...
--
Joel
next prev parent reply other threads:[~2012-03-27 13:56 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 [this message]
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
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=20120327135623.GC2701@adacore.com \
--to=brobecker@adacore.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