diff options
| author | Tim Wiederhake <tim.wiederhake@intel.com> | 2016-07-25 10:57:06 +0200 |
|---|---|---|
| committer | Tim Wiederhake <tim.wiederhake@intel.com> | 2016-07-25 11:03:43 +0200 |
| commit | c0272db5854a799a9f3bb3803c3d03d1a62b9ac2 (patch) | |
| tree | ebd295aa3734c916316b96ed8a1481e5d13c6c39 /opcodes | |
| parent | 95804507f2645c1cce29f2e1a33031accaa6aa24 (diff) | |
| download | gdb-c0272db5854a799a9f3bb3803c3d03d1a62b9ac2.zip gdb-c0272db5854a799a9f3bb3803c3d03d1a62b9ac2.tar.gz gdb-c0272db5854a799a9f3bb3803c3d03d1a62b9ac2.tar.bz2 | |
btrace: Resume recording after disconnect.
This patch allows gdbserver to continue recording after disconnect. On
reconnect, the recorded data is accessible to gdb as if no disconnect happened.
A possible application for this feature is remotely examine bugs that occur
at irregular intervals, where maintaining a gdb connection is inconvenient.
This also fixes the issue mentioned here:
https://sourceware.org/ml/gdb-patches/2015-11/msg00424.html
Signed-off-by: Tim Wiederhake <tim.wiederhake@intel.com>
gdb/ChangeLog:
* NEWS: Resume btrace on reconnect.
* record-btrace.c: Added record-btrace.h include.
(record_btrace_open): Split into this and ...
(record_btrace_push_target): ... this.
(record_btrace_disconnect): New function.
(init_record_btrace_ops): Use record_btrace_disconnect.
* record-btrace.h: New file.
* remote.c: Added record-btrace.h include.
(remote_start_remote): Check recording status.
(remote_btrace_maybe_reopen): New function.
gdb/doc/ChangeLog:
* gdb.texinfo: Resume btrace on reconnect.
gdb/testsuite/ChangeLog:
* gdb.btrace/reconnect.c: New file.
* gdb.btrace/reconnect.exp: New file.
Change-Id: I95e8b0ab8a89e58591aba0e63818cee82fd211bc
Diffstat (limited to 'opcodes')
0 files changed, 0 insertions, 0 deletions