This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch] testsuite: Fix "ERROR: no fileid for"
- From: "Maciej W. Rozycki" <macro at codesourcery dot com>
- To: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- Cc: <gdb-patches at sourceware dot org>
- Date: Thu, 6 Feb 2014 22:09:25 +0000
- Subject: Re: [patch] testsuite: Fix "ERROR: no fileid for"
- Authentication-results: sourceware.org; auth=none
- References: <20140206205814 dot GA18495 at host2 dot jankratochvil dot 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