From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Pedro Silva <psilva@pedrosilva.pt>
Cc: 25160@debbugs.gnu.org
Subject: bug#25160: 26.0.50; SIGSEGV when reading undo-tree file
Date: Mon, 11 Dec 2017 21:38:41 -0500 [thread overview]
Message-ID: <87609ceklq.fsf@users.sourceforge.net> (raw)
In-Reply-To: <87fulveof8.fsf@pedrosilva.pt> (Pedro Silva's message of "Sat, 10 Dec 2016 17:31:23 +0100")
merge 27779 25160
quit
Pedro Silva <psilva@pedrosilva.pt> writes:
> The undo-tree package produces some files that appear to, when read, SIGSEGV
> emacs. I've not been able to determine under which circumstances this happens.
>
> You should be able to replicate the issue by reconstructing the original
> directory structure, running 'emacs -Q', then loading the '.emacs' file
> below and attempting to open the source file at
> /home/psilva/src/pedrosilva/xs/src/xs.c (files attached.)
>
> /home/psilva/src/pedrosilva/xs/src/xs.c
> /home/psilva/.emacs.d/undo-tree/.!home!psilva!src!pedrosilva.pt!xs!src!xs.c.~undo-tree~
Using a recent emacs-26 build, when I open your C file, and load the
undo history you posted like this:
emacs-26/lucid/src/emacs -Q -l elpa/packages/undo-tree/undo-tree.el -f global-undo-tree-mode bug-25160-undo-tree-crash/xs.c --eval '(undo-tree-load-history "!home!psilva!src!pedrosilva.pt!xs!src!xs.c.~undo-tree~")'
I get
Re-entering top level after C stack overflow
So I think this is the same bug as #27779.
prev parent reply other threads:[~2017-12-12 2:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-10 16:31 bug#25160: 26.0.50; SIGSEGV when reading undo-tree file Pedro Silva
2016-12-10 19:57 ` Eli Zaretskii
2016-12-11 9:18 ` Pedro Silva
2016-12-11 15:32 ` Eli Zaretskii
2016-12-12 8:06 ` Pedro Silva
2016-12-12 16:11 ` Eli Zaretskii
2016-12-15 16:26 ` Eli Zaretskii
2017-12-12 2:38 ` Noam Postavsky [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87609ceklq.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=25160@debbugs.gnu.org \
--cc=psilva@pedrosilva.pt \
/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.