unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: mattiase@acm.org, 54501@debbugs.gnu.org, schwab@linux-m68k.org,
	monnier@iro.umontreal.ca, goldipox@mail.com
Subject: bug#54501: Segfault on recursive structure
Date: Sat, 26 Mar 2022 21:00:48 +0300	[thread overview]
Message-ID: <83r16oa90v.fsf@gnu.org> (raw)
In-Reply-To: <87tubkd67h.fsf@gnus.org> (message from Lars Ingebrigtsen on Sat,  26 Mar 2022 17:33:22 +0100)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Andy Gaynor <goldipox@mail.com>,  54501@debbugs.gnu.org,  Stefan Monnier
>  <monnier@iro.umontreal.ca>,  Andreas Schwab <schwab@linux-m68k.org>, Eli
>  Zaretskii <eliz@gnu.org>
> Date: Sat, 26 Mar 2022 17:33:22 +0100
> 
> Mattias Engdegård <mattiase@acm.org> writes:
> 
> > The patch fixes the #0=#0# nonsense as well since it's a trivial
> > check.
> 
> Thanks; seems to work perfectly.
> 
> Do you think this is safe enough to go on the release branch?
> 
> This isn't a regression (Emacs has segfaulted on the #0=[#1=(#0# . #1#)]
> as far back as I have Emacs versions), so I'd tend toward thinking it's
> not vital enough to install on the release branch, but perhaps Eli has a
> different opinion.  Eli?

I think we shouldn't install this on the release branch, it's too
risky, and the original problem has been with us forever, or
thereabouts.





      parent reply	other threads:[~2022-03-26 18:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-21 14:26 bug#54501: 27.2; to be disclosed in private Andy Gaynor
2022-03-22 14:44 ` bug#54501: Segfault on recursive structure Lars Ingebrigtsen
2022-03-22 15:02   ` Andreas Schwab
2022-03-22 15:04     ` Lars Ingebrigtsen
     [not found]       ` <trinity-1bb5c502-bafe-4a6c-b6be-08a2a1b27232-1648049044877@3c-app-mailcom-lxa04>
2022-03-25 15:34         ` Lars Ingebrigtsen
2022-03-26 15:58 ` Mattias Engdegård
2022-03-26 16:33   ` Lars Ingebrigtsen
     [not found]     ` <8F7060F3-8137-4835-873F-68E3F6B8010D@acm.org>
2022-03-26 17:43       ` Mattias Engdegård
2022-03-26 18:00     ` Eli Zaretskii [this message]

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=83r16oa90v.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=54501@debbugs.gnu.org \
    --cc=goldipox@mail.com \
    --cc=larsi@gnus.org \
    --cc=mattiase@acm.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=schwab@linux-m68k.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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).