mirror of
https://sourceware.org/git/binutils-gdb.git
synced 2024-12-01 05:55:23 +08:00
3d40fbb53b
Ref: https://sourceware.org/ml/gdb-patches/2015-08/msg00675.html If multiprocess extensions are off (because specific gdbserver port doesn't support them), then when gdbserver doesn't have a thread selected yet, and GDB sends Hg packet to select one, gdbserver crashes. That's because extracting the desired thread id out of the packet that GDB sent depends on the current thread to fill in the missing process id ... Fix this by getting the process id from the first (and only) process in the processes list instead. The GNU/Linux port doesn't trip on this because it always runs with multiprocess extensions enabled. To make it easier to catch such regressions going forward, this commit also adds a new smoke test that spawns gdbserver, connects to it and runs to main with the multiprocess extensions force-disabled. gdb/gdbserver/ChangeLog: 2015-08-24 Pedro Alves <palves@redhat.com> * inferiors.c (get_first_process): New function. * inferiors.h (get_first_process): New declaration. * remote-utils.c (read_ptid): Default to the first process in the list, instead of to the current thread's process. gdb/testsuite/ChangeLog: 2015-08-24 Pedro Alves <palves@redhat.com> * gdb.server/connect-without-multi-process.c: New file. * gdb.server/connect-without-multi-process.exp: New file. |
||
---|---|---|
.. | ||
connect-stopped-target.c | ||
connect-stopped-target.exp | ||
connect-without-multi-process.c | ||
connect-without-multi-process.exp | ||
ext-attach.c | ||
ext-attach.exp | ||
ext-restart.exp | ||
ext-run.exp | ||
ext-wrapper.exp | ||
file-transfer.exp | ||
Makefile.in | ||
no-thread-db.c | ||
no-thread-db.exp | ||
non-existing-program.exp | ||
server-exec-info.exp | ||
server-kill.c | ||
server-kill.exp | ||
server-mon.exp | ||
server-run.exp | ||
server.c | ||
solib-list-lib.c | ||
solib-list-main.c | ||
solib-list.exp | ||
transfer.txt | ||
wrapper.c | ||
wrapper.exp |