public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Keith Seitz <keiths@redhat.com>
Cc: archer@sourceware.org
Subject: Re: [Archer] Re: [Archer] Stop the Insanity! Linespec Rewrite
Date: Tue, 06 Mar 2012 17:40:00 -0000	[thread overview]
Message-ID: <20120306173945.GP2867@adacore.com> (raw)
In-Reply-To: <4F514E30.7070400@redhat.com>

Hi Keith,

Sorry for the delay in answering this...

> 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.]

Awesome, thanks!

> >   . 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.

OK. I have added two new testcases:

    * gdb.ada/bp_enum_homonym.exp: The testcase inserts a breakpoint
      using a function name ("archive"), but that name is also used
      as the name of one of the enumerals in an enumerated type.

    * gdb.ada/bp_on_var.exp: The testcase attempts to insert some
      breakpoints using variable names. The breakpoints should be
      rejected...

If you'd like me to take a look and tell you what's going on, I'd be
more than happy to...

-- 
Joel

  reply	other threads:[~2012-03-06 17:40 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     ` Joel Brobecker [this message]
2012-03-06 19:08       ` [Archer] " 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=20120306173945.GP2867@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).