diff options
| author | Alex Bennée <alex.bennee@linaro.org> | 2017-07-12 11:52:16 +0100 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2017-07-14 12:04:41 +0200 |
| commit | 5a6a1ad181c658b810041d852b290ac836965aca (patch) | |
| tree | f449069106dec8fb9cce3f220501a62bd714bbed /hw/alpha | |
| parent | bd88c780e6a17188f7fd676f3a056e5db21500e0 (diff) | |
| download | qemu-5a6a1ad181c658b810041d852b290ac836965aca.zip qemu-5a6a1ad181c658b810041d852b290ac836965aca.tar.gz qemu-5a6a1ad181c658b810041d852b290ac836965aca.tar.bz2 | |
gdbstub: don't fail on vCont; C04:0; c packets
The thread-id of 0 means any CPU but we then ignore the fact we find
the first_cpu in this case who can have an index of 0. Instead of
bailing out just test if we have managed to match up thread-id to a
CPU.
Otherwise you get:
gdb_handle_packet: command='vCont;C04:0;c'
put_packet: reply='E22'
The actual reason for gdb sending vCont;C04:0;c was fixed in a
previous commit where we ensure the first_cpu's tid is correctly
reported to gdb however we should still behave correctly next time it
does send 0.
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Reviewed-by: Greg Kurz <groug@kaod.org>
Reviewed-by: Claudio Imbrenda <imbrenda@linux.vnet.ibm.com>
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Message-Id: <20170712105216.747-5-alex.bennee@linaro.org>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'hw/alpha')
0 files changed, 0 insertions, 0 deletions