From: Joel Brobecker <brobecker@adacore.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] testsuite: false MI "unknown output after running" regression
Date: Fri, 01 Jan 2010 03:57:00 -0000 [thread overview]
Message-ID: <20100101035639.GN2788@adacore.com> (raw)
In-Reply-To: <20091231221942.GA4039@host0.dyn.jankratochvil.net>
> gdb/testsuite/
> 2009-12-31 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> * lib/mi-support.exp (mi_expect_stop <stopped at wrong place>): Insert
> missing $after_stopped and comma (,) expectation.
Phew, it took me a long time to understand how this patch could fix
the bad regexp on some of the examples you provided (the after_stop
field is empty), because I failed to notice that you added the missing
comma.
This looks right to me. Please go ahead an apply (I will rotate the
ChangeLog et al in a moment).
--
Joel
next prev parent reply other threads:[~2010-01-01 3:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-31 22:19 Jan Kratochvil
2010-01-01 3:57 ` Joel Brobecker [this message]
2010-01-01 8:02 ` Jan Kratochvil
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=20100101035639.GN2788@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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