From: Doug Evans <dje@google.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
Eli Zaretskii <eliz@gnu.org>,
gdb-patches@sourceware.org
Subject: Re: Regression for gdb.base/help.exp [Re: [PATCH v3] gdb: improve usage strings]
Date: Wed, 15 Aug 2012 16:27:00 -0000 [thread overview]
Message-ID: <CADPb22Qu8G6R7pY=mMUifw_=qaxJR8iW_pFNmB1ts3BeHWatKA@mail.gmail.com> (raw)
In-Reply-To: <201208151225.38921.vapier@gentoo.org>
On Wed, Aug 15, 2012 at 9:25 AM, Mike Frysinger <vapier@gentoo.org> wrote:
> On Wednesday 15 August 2012 03:22:11 Jan Kratochvil wrote:
>> On Wed, 15 Aug 2012 03:58:41 +0200, Mike Frysinger wrote:
>> > so i'll merge this and we can fight over improving it further if need be
>> > ;)
>>
>> Running ./gdb.base/help.exp ...
>> FAIL: gdb.base/help.exp: help finish
>> FAIL: gdb.base/help.exp: help jump
>> FAIL: gdb.base/help.exp: help next "n" abbreviation
>> FAIL: gdb.base/help.exp: help next
>> FAIL: gdb.base/help.exp: help nexti
>> FAIL: gdb.base/help.exp: help step "s" abbreviation
>> FAIL: gdb.base/help.exp: help step #1
>> FAIL: gdb.base/help.exp: help step #2
>> FAIL: gdb.base/help.exp: help stepi "si" abbreviation
>> FAIL: gdb.base/help.exp: help stepi
>> FAIL: gdb.base/help.exp: help signal
>
> ah, figures. i'll post a patch in a bit.
>
> btw, is there an easy way to run one specific .exp ? for gdb.base, i found i
> can cheat by doing:
> make check-gdb.base1 BASE1_FILES=gdb.base/help.exp
> but that seems like an awful hack and abuse of the current makefile ...
> -mike
make check RUNTESTFLAGS=foo.exp
next prev parent reply other threads:[~2012-08-15 16:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-11 16:55 [PATCH] gdb: improve usage strings Mike Frysinger
2012-08-11 17:16 ` Eli Zaretskii
2012-08-11 17:36 ` Mike Frysinger
2012-08-11 17:52 ` Eli Zaretskii
2012-08-11 18:08 ` Mike Frysinger
2012-08-14 15:08 ` Tom Tromey
2012-08-12 5:06 ` Doug Evans
2012-08-12 5:10 ` Mike Frysinger
2012-08-12 17:35 ` Eli Zaretskii
2012-08-13 2:06 ` [PATCH v2] " Mike Frysinger
2012-08-13 20:29 ` Doug Evans
2012-08-14 5:13 ` Mike Frysinger
2012-08-23 11:11 ` Pedro Alves
2012-08-14 5:29 ` [PATCH v3] " Mike Frysinger
2012-08-14 17:34 ` Doug Evans
2012-08-14 18:10 ` Eli Zaretskii
2012-08-15 1:58 ` Mike Frysinger
2012-08-15 7:22 ` Regression for gdb.base/help.exp [Re: [PATCH v3] gdb: improve usage strings] Jan Kratochvil
2012-08-15 16:25 ` Mike Frysinger
2012-08-15 16:27 ` Doug Evans [this message]
2012-08-20 4:29 ` Sergio Durigan Junior
2012-08-17 3:06 ` Mike Frysinger
2012-08-23 16:26 ` further improve "handle" help string Pedro Alves
2012-08-23 16:44 ` Eli Zaretskii
2012-08-23 17:18 ` Mike Frysinger
2012-08-23 17:38 ` Pedro Alves
2012-08-23 11:11 ` [PATCH v3] gdb: improve usage strings Pedro Alves
2012-08-23 16:45 ` Pedro Alves
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='CADPb22Qu8G6R7pY=mMUifw_=qaxJR8iW_pFNmB1ts3BeHWatKA@mail.gmail.com' \
--to=dje@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=vapier@gentoo.org \
/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