From: J K sanchez <1994jorgesanchez@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 47052@debbugs.gnu.org
Subject: bug#47052: 28.0.50; Segfault opening certain python file
Date: Wed, 10 Mar 2021 16:59:51 +0000 [thread overview]
Message-ID: <CAH873HBmgGi0Q6kn=SdqCsOaPC36UMPw+9aarPaNV762CfNimQ@mail.gmail.com> (raw)
In-Reply-To: <83lfavne2z.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1234 bytes --]
I found it's caused by this piece of code inside my ~/.emacs.d/init.el
(use-package undo-tree
:straight t
:config
;; autosave the undo-tree history
(setq undo-tree-history-directory-alist
`((".*" . ,temporary-file-directory)))
(setq undo-tree-auto-save-history t)
(global-undo-tree-mode +1)
:diminish 'undo-tree-mode)
El mié, 10 mar 2021 a las 16:55, Eli Zaretskii (<eliz@gnu.org>) escribió:
> > From: J K sanchez <1994jorgesanchez@gmail.com>
> > Date: Wed, 10 Mar 2021 15:54:03 +0000
> >
> > I found my emacs crashed when opening certain file. It's a python file i
> > can't share but other python files open nicely.
> > When using emacs -Q it opens without problems.
> > I found this in gdb when using bt full which was stuck in a loop and was
> too long.
> > a part of (gdb) bt full gives:
> > #30522 0x0000557f5a97f600 in substitute_object_recurse
> (subst=0x7ffd34af9380,
> > subtree=0x557f615b52d3) at lisp.h:730
>
> It's an infinite recursion, but I doubt we could do anything about it
> without a way to reproduce the problem. If you can somehow produce a
> file that is a derivative of the one you cannot share, and post it,
> that would be good.
>
> Thanks.
>
[-- Attachment #2: Type: text/html, Size: 1736 bytes --]
next prev parent reply other threads:[~2021-03-10 16:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 15:54 bug#47052: 28.0.50; Segfault opening certain python file J K sanchez
2021-03-10 16:55 ` Eli Zaretskii
2021-03-10 16:59 ` J K sanchez [this message]
2021-03-28 15:51 ` Lars Ingebrigtsen
2021-05-12 19:01 ` Lars Ingebrigtsen
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='CAH873HBmgGi0Q6kn=SdqCsOaPC36UMPw+9aarPaNV762CfNimQ@mail.gmail.com' \
--to=1994jorgesanchez@gmail.com \
--cc=47052@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 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).