GNU bug report logs - #17162
24.3; GDB interface stops working in some circumstances

Previous Next

Package: emacs;

Reported by: Zach Kost-Smith <zachkostsmith <at> gmail.com>

Date: Tue, 1 Apr 2014 15:51:06 UTC

Severity: normal

Tags: moreinfo

Found in version 24.3

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Zach Kost-Smith <zachkostsmith <at> gmail.com>
To: Barry OReilly <gundaetiapo <at> gmail.com>
Cc: 17162 <at> debbugs.gnu.org
Subject: bug#17162: 24.3; GDB interface stops working in some circumstances
Date: Tue, 1 Apr 2014 14:00:05 -0600
[Message part 1 (text/plain, inline)]
Hi Barry,

Perhaps there is some kind of misunderstanding?  M-x gud-gdb seems to
produce a prompt for gdb (have to remember not to use -i=mi for that one),
and it provides some simple support for setting breakpoints and printing
variables via the C-x C-a C-b / M-x gud-break sort of commands, but this
seems to be barely better than simpling running in a terminal.  There seems
to be no graphical representation of the point of execution, the location
of breakpoints either within the buffer or in a special breakpoint buffer,
nor a backtrace buffer, or the list of local variables (which is the only
one that I never really found very useful).

But, yes, using gud-gdb does not show the same behavior where a C-c C-c
will make the M-x gud-<something> commands stop working.  In some sense it
does indeed work better, but I have fond memories of a time where I think
that the GDB interface in Emacs was working.  Is there at least of
confirmation that others are seeing the same issue with things like M-x
gud-print stop working with M-x gdb?  I was troubleshooting with someone on
Reddit and they never saw this issue.

Zach



On Tue, Apr 1, 2014 at 1:39 PM, Barry OReilly <gundaetiapo <at> gmail.com> wrote:

> > we just stopped using GDB in Emacs long ago but I haven't given up
> > hope
>
> Does
>
>   M-x gud-gdb
>
> work better for you? The interface to GDB accessed via gdb command is
> dreadful.
>
> > As an aside, when troubleshooting this there seems to be more severe
> > but harder to reproduce issues where C-c C-c doesn't actually
> > interrupt the execution.
>
> Possibly related: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=16745
>
>
[Message part 2 (text/html, inline)]

This bug report was last modified 3 years and 310 days ago.

Previous Next


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