GNU bug report logs - #46439
26.1; command “break” within gdb afterwards run “list 1” infinitely

Previous Next

Package: emacs;

Reported by: galex-713 <at> galex-713.eu (Alexandre François Garreau)

Date: Thu, 11 Feb 2021 16:44:02 UTC

Severity: normal

Found in version 26.1

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

Bug is archived. No further changes may be made.

Full log


Message #8 received at 46439 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: galex-713 <at> galex-713.eu (Alexandre François Garreau)
Cc: 46439 <at> debbugs.gnu.org
Subject: Re: bug#46439: 26.1;
 command “break” within gdb afterwards run
 “list 1” infinitely
Date: Thu, 11 Feb 2021 19:05:52 +0200
> From: galex-713 <at> galex-713.eu (Alexandre François Garreau)
> Date: Thu, 11 Feb 2021 17:43:24 +0100
> 
> If I run M-x gdb and then within the GUD prompt type “b main:1” for
> instance (but it’ll be the same for any “break” command), it will print
> the classical “Breakpoint 1 at 0xXXXX: file file.c, line N.”, then will
> run “l 1” repeatedly while feeling the buffer with thousands of lines of
> the first ten lines of source file.  I don’t know why’s that, nor how to
> investigate.  I use the Debian GNU/Linux version.

I cannot reproduce this, neither in Emacs 26.1 nor in the current
development version.

Which version of GDB do you have?

And these messages might have something to do with the problem you
see:

> error in process filter: gdb-input: Process gud-commissaire-priseur not running
> error in process filter: Process gud-commissaire-priseur not running

Do you have some GUD customizations?  Does the problem happen in
"emacs -Q"?




This bug report was last modified 2 years and 340 days ago.

Previous Next


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