From: "Maciej W. Rozycki" <macro@codesourcery.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [patch] testsuite: Fix "ERROR: no fileid for"
Date: Thu, 06 Feb 2014 22:09:00 -0000 [thread overview]
Message-ID: <alpine.DEB.1.10.1402062122440.18199@tp.orcam.me.uk> (raw)
In-Reply-To: <20140206205814.GA18495@host2.jankratochvil.net>
On Thu, 6 Feb 2014, Jan Kratochvil wrote:
> a35cfb4007cee8cb84106412cd17f4e12f13345b is the first bad commit
> commit a35cfb4007cee8cb84106412cd17f4e12f13345b
> Author: Maciej W. Rozycki <macro@codesourcery.com>
> Date: Thu Oct 24 23:32:30 2013 +0100
>
> $ runtest gdb.base/solib-disc.exp
> Running ./gdb.base/solib-disc.exp ...
> ERROR: no fileid for host1
Thanks for your report and proposed fix. Can you provide a more
elaborate log of your test session? What are the exact conditions for
this problem to trigger?
I'm asking because I fear your change could defeat the purpose of the
commit you referred to if there's a catastrophic failure causing GDB to
crash while running gdb.base/solib-disc.exp -- in such a case an instance
of gdbserver would stay behind running, ruining the remaining part of the
test suite in environments where only a single TCP port is available for
the RSP connection.
Maciej
next prev parent reply other threads:[~2014-02-06 22:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 20:58 Jan Kratochvil
2014-02-06 22:09 ` Maciej W. Rozycki [this message]
2014-02-07 15:10 ` Jan Kratochvil
2014-02-16 18:10 ` Jan Kratochvil
2014-02-16 20:45 ` Maciej W. Rozycki
2014-02-16 20:51 ` [commit] " 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=alpine.DEB.1.10.1402062122440.18199@tp.orcam.me.uk \
--to=macro@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