all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: galex-713@galex-713.eu (Alexandre François Garreau)
Cc: 46439@debbugs.gnu.org
Subject: bug#46439: 26.1; command “break” within gdb afterwards run “list 1” infinitely
Date: Thu, 11 Feb 2021 19:05:52 +0200	[thread overview]
Message-ID: <83lfbuh6vj.fsf@gnu.org> (raw)
In-Reply-To: <87wnvemu6r.fsf@galex-713.eu>

> From: galex-713@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"?





  reply	other threads:[~2021-02-11 17:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-11 16:43 bug#46439: 26.1; command “break” within gdb afterwards run “list 1” infinitely Alexandre François Garreau
2021-02-11 17:05 ` Eli Zaretskii [this message]
     [not found]   ` <2094637.1ti1MOt0UP@galex-713.eu>
2021-02-11 20:35     ` Eli Zaretskii
2021-02-11 21:13       ` Alexandre Garreau
2021-02-12  6:50         ` Eli Zaretskii
2022-06-17 12:49           ` Lars Ingebrigtsen
2021-02-11 20:47   ` Alexandre Garreau

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83lfbuh6vj.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=46439@debbugs.gnu.org \
    --cc=galex-713@galex-713.eu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.