diff options
| author | Pedro Alves <palves@redhat.com> | 2015-11-30 16:05:18 +0000 |
|---|---|---|
| committer | Pedro Alves <palves@redhat.com> | 2015-11-30 18:39:12 +0000 |
| commit | 500c1d8576ad5a5bdc791fc7f7c3518a4d3f4b39 (patch) | |
| tree | 01c9ddf76e648f6e5b8153d84d569b07c0d79c79 /gdb/gdbserver/ChangeLog | |
| parent | de979965d3f5de7e4bf2354871fe85b3f77c720e (diff) | |
| download | gdb-500c1d8576ad5a5bdc791fc7f7c3518a4d3f4b39.zip gdb-500c1d8576ad5a5bdc791fc7f7c3518a4d3f4b39.tar.gz gdb-500c1d8576ad5a5bdc791fc7f7c3518a4d3f4b39.tar.bz2 | |
gdbserver crash if gdb attaches too fast
With "maint set target-non-stop on", the attach tests occasionally
crash gdbserver.
Basically, gdb attaches with vAttach;PID, and then shortly after reads
the xml target description for that process, to figure out the
process' architecture. On the gdbserver side, the target description
is only filled in when the first process/thread in the thread group
reports its initial PTRACE_ATTACH SIGSTOP. So if GDB is fast enough,
it can read the target description _before_ that initial stop, and
then gdbserver dies dereferencing a NULL tdesc pointer.
gdb/gdbserver/ChangeLog:
2015-11-30 Pedro Alves <palves@redhat.com>
* linux-low.c (linux_attach): In non-stop mode, wait for one stop
before returning.
Diffstat (limited to 'gdb/gdbserver/ChangeLog')
| -rw-r--r-- | gdb/gdbserver/ChangeLog | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/gdb/gdbserver/ChangeLog b/gdb/gdbserver/ChangeLog index 22d729f..3d694ac 100644 --- a/gdb/gdbserver/ChangeLog +++ b/gdb/gdbserver/ChangeLog @@ -1,5 +1,10 @@ 2015-11-30 Pedro Alves <palves@redhat.com> + * linux-low.c (linux_attach): In non-stop mode, wait for one stop + before returning. + +2015-11-30 Pedro Alves <palves@redhat.com> + * server.c (handle_v_requests): Handle vCtrlC. 2015-11-30 Pedro Alves <palves@redhat.com> |