mirror of
https://sourceware.org/git/binutils-gdb.git
synced 2024-11-30 21:44:19 +08:00
a0743c90c7
In extended-remote, when GDB connects the target, but target is not running, the TSVs are not uploaded. When GDB attaches to a process, the TSVs are not uploaded either. However, GDBserver has some builtin or predefined TSV to upload, such as $trace_timestamp. This bug causes $trace_timestamp is never uploaded. gdb/ 2013-06-25 Yao Qi <yao@codesourcery.com> * remote.c (remote_start_remote): Move code to upload tsv earlier. gdb/testsuite/ 2013-06-25 Yao Qi <yao@codesourcery.com> * boards/native-extended-gdbserver.exp: Set board_info 'gdb,predefined_tsv'. * boards/native-gdbserver.exp: Likewise. * boards/native-stdio-gdbserver.exp: Likewise. * gdb.server/ext-attach.exp: Load trace-support.exp. Check uploaded TSVs if target supports tracing. * gdb.trace/tsv.exp: Check uploaded TSVs if target supports tracing and target has predefined tsv. gdb/doc/ 2013-06-25 Yao Qi <yao@codesourcery.com> * gdbint.texinfo (Testsuite): Document 'gdb,predefined_tsv'. |
||
---|---|---|
.. | ||
ext-attach.c | ||
ext-attach.exp | ||
ext-run.exp | ||
file-transfer.exp | ||
Makefile.in | ||
no-thread-db.c | ||
no-thread-db.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 |