This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 5/6] testsuite: Introduce $inferior_spawn_id
- From: Antoine Tremblay <antoine dot tremblay at ericsson dot com>
- To: Pedro Alves <palves at redhat dot com>, Yao Qi <qiyaoltc at gmail dot com>
- Cc: <gdb-patches at sourceware dot org>
- Date: Thu, 16 Apr 2015 12:55:27 -0400
- Subject: Re: [PATCH 5/6] testsuite: Introduce $inferior_spawn_id
- Authentication-results: sourceware.org; auth=none
- References: <1424699660-11727-1-git-send-email-palves at redhat dot com> <1424699660-11727-6-git-send-email-palves at redhat dot com> <867fv7xodw dot fsf at gmail dot com> <54F04A2B dot 5 at redhat dot com> <54F05E34 dot 7070401 at gmail dot com> <54F06341 dot 5080501 at redhat dot com>
I have a question regarding noinferiorio and it's future usage...
As the condition with noinferiorio in interrupt.exp is now :
if {[target_info exists gdb,noinferiorio] && $inferior_spawn_id ==
$gdb_spawn_id}
noinferiorio is effectively bypassed when we are using gdbserver, even
as noinferirorio is true.
But what if the board or simulator really can't handle io at all, and
that setvbuf would not work.. then there is no option to disable io
tests in that case ?
Is the intention to remove noinferiorio from gdbserver-base.exp and keep
the tests with the if {[target_info exists gdb,noinferiorio]} check ?
Regards,
Antoine