This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 00/23] Multi-target support
- From: Pedro Alves <palves at redhat dot com>
- To: Philippe Waroquiers <philippe dot waroquiers at skynet dot be>, gdb-patches at sourceware dot org
- Date: Wed, 16 Oct 2019 20:08:47 +0100
- Subject: Re: [PATCH 00/23] Multi-target support
- References: <20190906232807.6191-1-palves@redhat.com> <2802fb1954a3756ec7e507141652b8d92127424a.camel@skynet.be> <6bed10d6-482f-917d-54f5-34c079ee9547@redhat.com> <6c1828abbbfda76da123926fda8b37816132075a.camel@skynet.be>
On 9/8/19 9:50 PM, Philippe Waroquiers wrote:
>>> (gdb) infer 1
>>> [Switching to inferior 1 [Remote target]
>>> (/home/philippe/valgrind/git/trunk_untouched/memcheck/tests/trivialleak)]
>>> [Switching to thread 1.1 (Thread 10050)]
>>> #0 0x0000000004001090 in _start () from /lib64/ld-linux-x86-64.so.2
>>> (gdb) c
>>> Continuing.
>>> Connection 2 (remote lvgdb --pid=16727) does not support multi-target resumption.
>>> (gdb)
>>>
>>> So, the continue command is refused both in inferior 1 and inferior 2.
I've finally debugged this, it was a simple bug in target.c. We need this:
@@ -2181,7 +2181,7 @@ user_visible_resume_ptid (int step)
process_stratum_target *
user_visible_resume_target (ptid_t resume_ptid)
{
- return (resume_ptid == minus_one_ptid
+ return (resume_ptid == minus_one_ptid && sched_multi
? NULL
: current_inferior ()->process_target ());
I'm folding that into the main multi-target patch, which introduces
that function.
Thanks,
Pedro Alves