all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alexandre Garreau <galex-713@galex-713.eu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 46439@debbugs.gnu.org
Subject: bug#46439: 26.1; command “break” within gdb afterwards run “list 1” infinitely
Date: Thu, 11 Feb 2021 22:13:48 +0100	[thread overview]
Message-ID: <2157736.a3s1I0Q0vf@galex-713.eu> (raw)
In-Reply-To: <835z2ygx6w.fsf@gnu.org>

Le jeudi 11 février 2021, 21:35:03 CET Eli Zaretskii a écrit :
> [Please use Reply All to keep the bug tracker CC'ed on all messages.]
> 
> > From: Alexandre Garreau <galex-713@galex-713.eu>
> > Date: Thu, 11 Feb 2021 21:22:16 +0100
> > 
> > Turned out the *minimal* requirement to reproduce are: compiling with
> > debugging symbols AND doing that in a directory containing
> > a non-ascii character (which will end inside the binary, and create
> > the
> > problem even if you’re not anymore in a such path afterward).
> 
> Ah, that one...  This is already fixed in later Emacs versions, part
> of it in Emacs 27 and the rest on the master branch.  Can you try a
> newer Emacs version?

Not now, too long to compile afair, and I heard about stability and memory 
leaks issues about 27 on #emacs.  Could you reproduce?  Or maybe it’s 
likely solved and not worth it.  Anyway thank you, sorry for the time loss 
then '^^





  reply	other threads:[~2021-02-11 21:13 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
     [not found]   ` <2094637.1ti1MOt0UP@galex-713.eu>
2021-02-11 20:35     ` Eli Zaretskii
2021-02-11 21:13       ` Alexandre Garreau [this message]
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=2157736.a3s1I0Q0vf@galex-713.eu \
    --to=galex-713@galex-713.eu \
    --cc=46439@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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.