[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: gdbstub.c CPU clusters not handled for ThreadInfo packets
From: |
Fabien Chouteau |
Subject: |
Re: gdbstub.c CPU clusters not handled for ThreadInfo packets |
Date: |
Fri, 5 Jun 2020 12:47:54 +0200 |
On Tue, Jun 2, 2020 at 7:26 PM Peter Maydell <peter.maydell@linaro.org> wrote:
> When there's multiple clusters, by default gdb will show you all the CPUs in
> the first
> cluster. Would the behaviour be better if the other cluster in
> this machine was the first (default) one?
For our use case yes it would be better. I will look to see if this is
doable with a small patch on our fork.
> Hmm. That's the behavior for 'target remote' but 'target extended-remote'
> ought to support multiple inferiors. What gdb version is this?
Force of habit, I made a fool of myself and used only 'target remote'.
Sorry for the noise here.
Thanks for your help,