This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [pushed] Fix gdbserver/MI testing regression
- From: Simon Marchi <simon dot marchi at ericsson dot com>
- To: Pedro Alves <palves at redhat dot com>, <gdb-patches at sourceware dot org>
- Date: Mon, 4 Jul 2016 13:22:16 -0400
- Subject: Re: [pushed] Fix gdbserver/MI testing regression
- Authentication-results: sourceware.org; auth=none
- References: <1462538104-19109-1-git-send-email-palves@redhat.com> <1462538104-19109-32-git-send-email-palves@redhat.com> <5772DBCA.4090802@ericsson.com> <813555f3-c917-cd95-6d41-3ec64cad2cf6@redhat.com> <14e113dd-0488-79d0-6cde-82cdb1562793@redhat.com>
On 16-06-30 07:12 AM, Pedro Alves wrote:
> On 06/29/2016 11:50 AM, Pedro Alves wrote:
>> On 06/28/2016 09:19 PM, Simon Marchi wrote:
>>> I added a few traces to understand what's happening, and it seems that inferior_spawn_id
>>> is being unset at two places:
>
> Indeed.
>
>>> The easy way would be to add a "info exists" check before unsetting it, but I don't know if
>>> that would only hide a real problem.
>
> I went ahead and pushed the patch below, with takes an even easier route.
>
> I think we'll need to do something better in at least a couple scenarios:
>
> - If/when gdbserver learns about "set inferior-tty", the separate
> inferior tty spawn id should be used instead of gdbserver's. gdbserver
> doesn't support that, so in tests that use that (or MI's equivalent),
> inferior output indeed is sent to gdbserver's tty.
>
> - Tests that disconnect from gdbserver/restart gdb/reconnect to gdbserver
> should end up inferior_spawn_id set to gdbserver's spawn id,
> otherwise tests that rely on inferior I/O, after the reconnect won't work
> properly. I think there's no such test currently, though, so I'm ignoring
> this for now.
Thanks! Your patch fixes the problem I initially encountered.
Simon