GNU bug report logs - #13303
24.2.91; gdb under emacs broken for break commands

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stephen Leake <stephen_leake <at> stephe-leake.org>
Cc: 13303 <at> debbugs.gnu.org
Subject: bug#13303: 24.2.91; gdb under emacs broken for break commands
Date: Sat, 29 Dec 2012 10:17:24 +0200

> Date: Fri, 28 Dec 2012 23:04:21 -0500
> From: Stephen Leake <stephen_leake <at> stephe-leake.org>
> 
> M-x gdb
> Run gdb (like this): gdb -i=mi hello
> 
> at the gdb prompt, set a breakpoint:
> break hello.c:4
> 
> try to set commands:
> command 1
> 
> should see a prompt, terminate by 'end'. Instead, see:
> (gdb) command 1
> Type commands for breakpoint(s) 1, one per line.
> End with a line saying just "end".

Aren't the last 2 lines the prompt you expected to see?  If not, what
prompt did you expect?  What do you see when you run the same GDB
commands from the shell prompt?

> p argc
> end
> p argc
> end
> (gdb)
> 
> This was terminated by Menu | Signals | EOF

Why did you send EOF?  That command causes the debugger to quit, so
what's the purpose of sending it here?

> On Windows 7, the behavior is slightly different; the '>' prompt is
> visible, but EOF crashes gdb.

Not really a crash, at least on my XP SP3.  It exits after reporting
some weird error message about stdin, which is expected, since Emacs
closes the debugger's stdin file descriptor.  What kind of "crash" did
you see on Windows 7?

Anyway, the annoyance with no "> " prompt on Posix hosts is a known
problem with GDB versions older than 7.5; see bug#11279.  You can work
around it by typing this command at the first GDB prompt:

  (gdb) set interactive-mode off

GDB 7.5 fixed that problem, so upgrading your GDB will remove the need
to use the above work-around.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.