From: Pedro Alves <pedro@codesourcery.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Fix gdb.mi internal_error on killing inferior
Date: Thu, 21 May 2009 16:03:00 -0000 [thread overview]
Message-ID: <200905211703.24047.pedro@codesourcery.com> (raw)
In-Reply-To: <20090521084235.GA3217@host0.dyn.jankratochvil.net>
On Thursday 21 May 2009 09:42:35, Jan Kratochvil wrote:
> On Thu, 21 May 2009 02:42:10 +0200, Pedro Alves wrote:
> > This patches fixes your test above for me. I'm running
> > the full testsuite on {sync|async}/{remote|native}, after
> > having run a few smoke test .exp's and seeing no problem.
> > Does it work for you?
>
> Yes, it fixes the problem I did see. No regressions on my system.
Great, many thanks. I've checked it in. My testing looked good too.
With the spurious prompt fixed, running the whole testsuite in async
mode gives the same results as it used to before these breakages.
--
Pedro Alves
prev parent reply other threads:[~2009-05-21 16:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-20 20:28 Jan Kratochvil
2009-05-20 20:43 ` Pedro Alves
2009-05-20 21:36 ` Jan Kratochvil
2009-05-21 0:41 ` Pedro Alves
2009-05-21 8:44 ` Jan Kratochvil
2009-05-21 16:03 ` Pedro Alves [this message]
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=200905211703.24047.pedro@codesourcery.com \
--to=pedro@codesourcery.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