Re: gdb "command" broken with -mi

[Ryan Johnson <ryan.johnson@cs.utoronto.ca>]

On 20/08/2013 10:35 AM, Eli Zaretskii wrote:
>> Date: Tue, 20 Aug 2013 08:55:54 -0400
>> From: Ryan Johnson <ryan.johnson@cs.utoronto.ca>
>>
>> I noticed during a recent debug session that gdb's "command" command
>> (setting actions to perform when a breakpoint triggers) doesn't work.
>> You can start to enter the list of commands, but emacs ignores the "end"
>> keyword that should terminate the list, forcing you to cancel the
>> attempt with C-c C-c.
>>
>> Is this a known issue?
> This used to be a problem in older versions of Emacs, but it was fixed
> more than a year ago, and all versions of Emacs from 24.3 (inclusive)
> onwards should not fail this way.  What version of Emacs are you
> using?
>
> FWIW, I've just tried this in yesterday's trunk, and it works for me
> in a simple test case.
I'm using 24.3.2 with Ken's cygwin patches.

The STC is:
1. gcc -g -ostc -xc <(echo "int main() { return 0; }")
2. Fire up emacs M-x gdb and point it at stc
3. b main
4. comm 1
> Reading symbols from /home/Ryan/experiments/a.exe...done.
> (gdb) b main
> Breakpoint 1 at 0x1004010dd: file stc.c, line 2.
> (gdb) comm 1
> Type commands for breakpoint(s) 1, one per line.
> End with a line saying just "end".
> >p $pc
> >end
> >
> >
> >  C-c C-cQuit
> (gdb)

If it's fixed in later versions, though, maybe Ken's (hopefully 
soon-arriving) cygwin package update that fixes the stack overflow 
problem will also pick up this fix.

Thanks,
Ryan