[Bug mi/28711] gdb closes when displaying structs with long field names in eclipse

["jonah at kichwacoders dot com" <sourceware-bugzilla@sourceware.org>]

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

Jonah Graham <jonah at kichwacoders dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jonah at kichwacoders dot com

--- Comment #12 from Jonah Graham <jonah at kichwacoders dot com> ---
@Andrew,

I am concerned that the fix for this issue has caused a regression on Windows
that breaks Eclipse CDT in a new way. I don't have a setup to build GDB for
Windows, but the user reported trying the ARM pre-built one and I can reproduce
the problem with it.
https://github.com/eclipse-embed-cdt/eclipse-plugins/issues/546

Here is a little snippet that demonstrates the problem:

$ cat input
1234-list-thread-gro
5678-list-thread-gro
9012-list-thread-gro

$ cat input | ./arm-none-eabi-gdb --silent --interpreter=mi2
=thread-group-added,id="i1"
(gdb)
1234^error,msg="Undefined MI command: list-thread-gro",code="undefined-command"
(gdb)
678^error,msg="Undefined MI command: list-thread-gro",code="undefined-command"
(gdb)
9012^error,msg="Undefined MI command: list-thread-gro",code="undefined-command"
(gdb)

As you can see above the 5 (in 5678) is missing. The commands
(-list-thread-gro)  is incorrect on purpose as the length of the command and
the newline of the input file all seem to affect whether or not this problem is
seen.

This is also printed at the end of the run, but I think that is because of EOF
on input:
&"warning: Exception condition detected on fd 0\n"
&"error detected on stdin\n"

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