Upload tsv earlier in remote_start_remote
authorYao Qi <yao@codesourcery.com>
Tue, 25 Jun 2013 13:01:28 +0000 (13:01 +0000)
committerYao Qi <yao@codesourcery.com>
Tue, 25 Jun 2013 13:01:28 +0000 (13:01 +0000)
commita0743c90c7c48938c0bd80fc3aa316e90ee26495
treeb7b4c64341eb6f9ffedeb7b249d6b7a1a5f180bc
parent9d6e6e84f73ef7c5410c097a23d5952a99684f5b
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'.
gdb/ChangeLog
gdb/doc/ChangeLog
gdb/doc/gdbint.texinfo
gdb/remote.c
gdb/testsuite/ChangeLog
gdb/testsuite/boards/native-extended-gdbserver.exp
gdb/testsuite/boards/native-gdbserver.exp
gdb/testsuite/boards/native-stdio-gdbserver.exp
gdb/testsuite/gdb.server/ext-attach.exp
gdb/testsuite/gdb.trace/tsv.exp
This page took 0.026477 seconds and 4 git commands to generate.