[Bug mi/17109] gdb 7.7 crashes when issuing mi command: -trace-frame-collected

["qiyao at gcc dot gnu.org" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=17109

Yao Qi <qiyao at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |qiyao at gcc dot gnu.org

--- Comment #1 from Yao Qi <qiyao at gcc dot gnu.org> ---
I can't reproduce it on gdb 7.7 with gdbserver:

(gdb) trace start
Tracepoint 1 at 0x8048483: file
../../../../git/gdb/testsuite/gdb.trace/read-memory.c, line 28.
(gdb) actions 
Enter actions for tracepoint 1, one per line.
End with a line saying just "end".
>collect testglob
>collect constglob
>end
(gdb) b end
Breakpoint 2 at 0x8048488: file
../../../../git/gdb/testsuite/gdb.trace/read-memory.c, line 32.
(gdb) tstart 
(gdb) c
Continuing.

Breakpoint 2, end () at
../../../../git/gdb/testsuite/gdb.trace/read-memory.c:32
32      {}
(gdb) tstop 
(gdb) tfind start
Found trace frame 0, tracepoint 1
#0  start () at ../../../../git/gdb/testsuite/gdb.trace/read-memory.c:28
28      {}
(gdb) interpreter-exec mi "-trace-frame-collected"
^done,explicit-variables=[{name="testglob",value="1"},{name="constglob",value="10000"}],computed-expressions=[],registers=[{number="8",value="0x8048483"}],tvars=[],memory=[{address="0x08048574",length="4"},{address="0x0804a020",length="4"}]

The backtrace of GDB when it crashes would be helpful.

-- 
You are receiving this mail because:
You are on the CC list for the bug.