From: Keith Seitz <keiths@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: archer@sourceware.org
Subject: Re: [Archer] Stop the Insanity! Linespec Rewrite
Date: Fri, 02 Mar 2012 22:49:00 -0000 [thread overview]
Message-ID: <4F514E30.7070400@redhat.com> (raw)
In-Reply-To: <20120302190658.GH2867@adacore.com>
On 03/02/2012 11:06 AM, Joel Brobecker wrote:
> I reviewed the gdb.ada testsuite, and it appears that I failed to
> add a testcase for those. I will put that on my list.
I have a patch to fix this. Thank you for bringing this to my attention
(and adding tests for it). Your new operator_bps.exp passes 100% on
archer-keiths-linespec-rewrite. [I haven't pushed the patch yet.]
> I have noticed a few other things:
>
> . Very minor: We now accept the "task" keyword in any casing (?).
> So now "break foo TASK 3" is accepted, whereas it wasn't in the past.
I need to audit that. Part of the cleanup phase. Lots to do yet.
> . Our testsuite spotted a couple of crashes. They might be related
> to the crash that Tom mentioned, although I kind of doubt it.
> Nevertheless, I'll investigate them after you've looked at Tom's
> report, just in case they end up having the same cause.
If you can tell me how to reproduce, I will take a look. There are
probably lots of gotchas all over the place. I relied heavily (too
much?) on the test suite. I wonder what bugs Go, D, and other languages
might expose.
> I'd like to resolve the issues mentioned above before the patch
> actually goes in, [...]
Absolutely. I would not even think of submitting this for official
review if it had any (real) regressions.
Thank you very much for your help.
Keith
next prev parent reply other threads:[~2012-03-02 22:49 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 [this message]
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
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=4F514E30.7070400@redhat.com \
--to=keiths@redhat.com \
--cc=archer@sourceware.org \
--cc=brobecker@adacore.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).