Yao Qi a0743c90c7 Upload tsv earlier in remote_start_remote ... 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'.		2013-06-25 13:01:28 +00:00
..
a4rc.sed
agentexpr.texi
all-cfg.texi
annotate.texinfo
ChangeLog	Upload tsv earlier in remote_start_remote	2013-06-25 13:01:28 +00:00
fdl.texi
gdb.texinfo	Teach -data-list-register-values to not include unavailable registers	2013-06-20 00:39:11 +00:00
gdbint.texinfo	Upload tsv earlier in remote_start_remote	2013-06-25 13:01:28 +00:00
gpl.texi
lpsrc.sed
LRS
Makefile.in	don't keep a gdb-specific date	2013-06-24 15:06:27 +00:00
observer.texi
psrc.sed
refcard.tex
stabs.texinfo
stack_frame.eps
stack_frame.pdf
stack_frame.png
stack_frame.svg
stack_frame.txt