XEmacs exiting to debugger. Fatal error: assertion failed, file emacs.c, line 3513, ABORT() Fatal error (6). Your files have been auto-saved. ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.1_no_multilib_hardened-j4-20211011-040203 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-11.2.0 * clang version 13.0.0 Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/lib/llvm/13/bin /usr/lib/llvm/13 13.0.0 Python 3.9.7 Available Ruby profiles: [1] ruby26 (with Rubygems) [2] ruby27 (with Rubygems) [3] ruby30 (with Rubygems) * Available Rust versions: [1] rust-bin-1.55.0 [2] rust-1.55.0 * The following VMs are available for generation-2: The Glorious Glasgow Haskell Compilation System, version 8.10.4 php cli: HEAD of ::gentoo commit cd7f0332eba12ea03fdcf333a8f41312dfeec956 Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Sat Oct 16 20:21:31 2021 +0000 2021-10-16 20:21:29 UTC emerge -qpvO app-editors/xemacs [ebuild U ] app-editors/xemacs-21.5.34-r7 [21.5.34-r6] USE="-X -Xaw3d -alsa -athena -berkdb -debug -dnd -eolconv -freewnn -gdbm -gif -gpm -jpeg -ldap -motif -mule -nas -neXt -png -pop -postgres -tiff -xface -xft -xim"
Created attachment 745314 [details] emerge-info.txt
Created attachment 745317 [details] app-editors:xemacs-21.5.34-r7:20211016-203115.log
Created attachment 745320 [details] emerge-history.txt
Created attachment 745323 [details] environment
Created attachment 745326 [details] etc.portage.tar.bz2
Created attachment 745329 [details] logs.tar.bz2
Created attachment 745332 [details] temp.tar.bz2
I have asked upstream for help on this.
(In reply to Mats Lidell from comment #8) > I have asked upstream for help on this. a -9999 builds fine here at the affected image (42 packages were updated as a dep before FWIW, including glibc).
(In reply to Toralf Förster from comment #9) > a -9999 builds fine here at the affected image (42 packages were updated as > a dep before FWIW, including glibc). Thanks for testing with the tip upstream version. Would it be possible for you to test this reported config with xemacs-21.5.34-r9 where back ported changes from upstream has been applied? Or would just closing it be OK and referring to that changes that might affect this problem has been applied to that ebuild?
closing is fully ok