GNU bug report logs -
#56794
Segmentation fault in purecopy while dumping - stack overflow attempting to copy cyclic Lisp value
Previous Next
Reported by: Lynn Winebarger <owinebar <at> gmail.com>
Date: Wed, 27 Jul 2022 14:08:01 UTC
Severity: normal
Done: Stefan Kangas <stefankangas <at> gmail.com>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your bug report
#56794: Segmentation fault in purecopy while dumping - stack overflow attempting to copy cyclic Lisp value
which was filed against the emacs package, has been closed.
The explanation is attached below, along with your original report.
If you require more details, please reply to 56794 <at> debbugs.gnu.org.
--
56794: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=56794
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
Lynn Winebarger <owinebar <at> gmail.com> writes:
> I apologize for not being able to include significant details of the build, as this is happening on a
> sandboxed system in a proprietary context.
> I've been attempting to dump emacs built from the 28.1 tarball with a large number of core libraries
> preloaded. I have observed segmentation faults when attempting to dump with native-compilation
> enabled and with native-compilation disabled. However, it only happened with one file
> (nxml/rng-pttrn.el) while dumping several hundred core libraries with native compilation. With native
> compilation disabled, the problem has appeared with both auth-source.el and
> emacs-lisp/eieio-core.el, the latter preventing me from proceeding much further in the dump process.
> Note these were both dumped successfully with native-compilation enabled.
> I used gdb to look at the backtrace after the segmentation fault while loading auth-source.el, and the
> stack was in a tight recursive loop in purecopy:
>
> for (i = 0; i < size; i++)
>
> vec->contents[i] = purecopy (vec->contents[i]);
>
> In this case the index I alternated between two values in each pair of stack frames: 0 and 10.
> I'm not familiar enough with the layout of lisp objects to recognize the pseudo vector type on site, but
> it's probably a byte-vector with a recursive call - the constants vector in slot 0, and the recursive
> binding in slot 10 of the constants vector. Plus, the fact that this started happening more frequently
> with byte-compilation only is suspicious in itself.
> Since I'm restricted to using official release tarballs with only local modifications, I'd welcome any
> hints on any "quick fix" to the problem aside from the long-term solution of just eliminating purecopy
> altogether (unless that can be done with a de minimis change to the code).
With the removal of purespace on master, `purecopy' is now an alias for
`identity', so I don't think there's anything more to do here. Thanks
for reporting it, nevertheless.
I'm therefore closing this bug report.
[Message part 3 (message/rfc822, inline)]
[Message part 4 (text/plain, inline)]
I apologize for not being able to include significant details of the build,
as this is happening on a sandboxed system in a proprietary context.
I've been attempting to dump emacs built from the 28.1 tarball with a large
number of core libraries preloaded. I have observed segmentation faults
when attempting to dump with native-compilation enabled and with
native-compilation disabled. However, it only happened with one file
(nxml/rng-pttrn.el) while dumping several hundred core libraries with
native compilation. With native compilation disabled, the problem has
appeared with both auth-source.el and emacs-lisp/eieio-core.el, the latter
preventing me from proceeding much further in the dump process. Note these
were both dumped successfully with native-compilation enabled.
I used gdb to look at the backtrace after the segmentation fault while
loading auth-source.el, and the stack was in a tight recursive loop in
purecopy:
for (i = 0; i < size; i++)
vec->contents[i] = purecopy (vec->contents[i]);
In this case the index I alternated between two values in each pair of
stack frames: 0 and 10.
I'm not familiar enough with the layout of lisp objects to recognize the
pseudo vector type on site, but it's probably a byte-vector with a
recursive call - the constants vector in slot 0, and the recursive binding
in slot 10 of the constants vector. Plus, the fact that this started
happening more frequently with byte-compilation only is suspicious in
itself.
Since I'm restricted to using official release tarballs with only local
modifications, I'd welcome any hints on any "quick fix" to the problem
aside from the long-term solution of just eliminating purecopy altogether
(unless that can be done with a de minimis change to the code).
Lynn
[Message part 5 (text/html, inline)]
This bug report was last modified 103 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.