Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: msnyder@redhat.com, muller@cerbere.u-strasbg.fr
Cc: ac131313@cygnus.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA]Use prev_lexptr in *-exp.y
Date: Fri, 03 May 2002 06:52:00 -0000	[thread overview]
Message-ID: <200205031352.g43DqHB15897@duracef.shout.net> (raw)

Pierre Muller writes:
> By the way, I don't have the necessary stuff to run the 
> testsuite... Thus I can not warranty that there are no 
> regressions. There mught be some wrong regressions,
> if some testsuite do check the error output in case of 
> wrong expression entered. The error output should be more
> logical now, but could get some tests  to fail.

Pierre,

I have that covered.  I run the test suite every 5-10 days on many
configurations, and I have a good procedure for diff'ing the results
and finding regressions.  So if there are changes in the gdb output and
they cause regressions in the test suite then I will catch them and post
detailed bug reports.

Michael C


             reply	other threads:[~2002-05-03 13:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-03  6:52 Michael Elizabeth Chastain [this message]
2002-05-03 10:43 ` Michael Snyder
  -- strict thread matches above, loose matches on Subject: below --
2002-05-07  8:08 Michael Elizabeth Chastain
2002-05-07  8:59 ` Petr Sorfa
2002-05-03 14:59 Michael Elizabeth Chastain
2002-05-03 16:23 ` Michael Snyder
2002-05-07  7:45 ` Petr Sorfa
2002-04-25  8:06 [PATCH]Use prev_lexptr in p-exp.y Pierre Muller
2002-04-25  8:30 ` Andrew Cagney
2002-04-25  9:49   ` [RFA]Use prev_lexptr in *-exp.y Pierre Muller
2002-04-25 11:51     ` Michael Snyder
2002-05-02  6:33       ` Pierre Muller
2002-05-02 11:02         ` Michael Snyder
2002-05-03  1:38           ` Pierre Muller
2002-05-03 10:41             ` Michael Snyder

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=200205031352.g43DqHB15897@duracef.shout.net \
    --to=mec@shout.net \
    --cc=ac131313@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=msnyder@redhat.com \
    --cc=muller@cerbere.u-strasbg.fr \
    /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