diff options
| author | Jan Vrany <jan.vrany@labware.com> | 2021-02-25 16:22:13 +0000 |
|---|---|---|
| committer | Jan Vrany <jan.vrany@labware.com> | 2021-02-25 16:22:13 +0000 |
| commit | 2450ad54ce04376d354acc948a52aa0f5efed56b (patch) | |
| tree | b19020dabd626124ecc81ec6902c2b39562cef4c /gdb/stack.c | |
| parent | 30c80d8833c037f25dd144a64f7f8b7b3ab19027 (diff) | |
| download | gdb-2450ad54ce04376d354acc948a52aa0f5efed56b.zip gdb-2450ad54ce04376d354acc948a52aa0f5efed56b.tar.gz gdb-2450ad54ce04376d354acc948a52aa0f5efed56b.tar.bz2 | |
gdb/mi: Remove extra \n from tsv and and traceframe notifications
An extra \n in calls to fprintf_unfiltered() caused invalid MI records
to be emitted:
> gdb -i mi3 -ex "target remote :7000"
=thread-group-added,id="i1"
~"GNU gdb (GDB) 11.0.50.20201019-git\n"
~"Copyright (C) 2020 Free Software Foundation, Inc.\n"
...
~"Remote debugging using :7001\n"
=tsv-created,name="trace_timestamp",initial="0"\n
=thread-group-started,id="i1",pid="304973"
This commit fixes the problem.
gdb/ChangeLog:
* gdb/mi/mi-interp.c (mi_traceframe_changed): Remove trailing \n from output.
(mi_tsv_created): Likewise.
(mi_tsv_deleted): Likewise.
Diffstat (limited to 'gdb/stack.c')
0 files changed, 0 insertions, 0 deletions