GNU bug report logs -
#58226
29.0.50; multisession-tests.el fails to finish on macOS (10.13.6)
Previous Next
Reported by: Stefan Kangas <stefankangas <at> gmail.com>
Date: Sat, 1 Oct 2022 14:26:03 UTC
Severity: normal
Found in version 29.0.50
Done: Stefan Kangas <stefankangas <at> gmail.com>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 58226 in the body.
You can then email your comments to 58226 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#58226
; Package
emacs
.
(Sat, 01 Oct 2022 14:26:03 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Stefan Kangas <stefankangas <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Sat, 01 Oct 2022 14:26:03 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Failed test on macOS 10.13.6, see below output from "make check":
/bin/sh: line 1: 94619 Abort trap: 6 HOME=/nonexistent
LANG=C EMACS_TEST_DIRECTORY=/Users/skangas/wip/emacs/test
"../src/emacs" --module-assertions --no-init-file --no-site-file
--no-site-lisp -L ":." -l ert -l lisp/emacs-lisp/multisession-tests
--batch --eval '(ert-run-tests-batch-and-exit (quote (not (or (tag
:expensive-test) (tag :unstable)))))' >
lisp/emacs-lisp/multisession-tests.log 2>&1
Running 5 tests (2022-10-01 16:13:27+0200, selector ‘(not (or (tag
:expensive-test) (tag :unstable)))’)
multisession--sbar 1
multisession--sbar 1
multisession--sbar 1
multisession--sbar 1
multisession--sbar 1
multisession--sbar 4
multisession--sbar 28
multisession--sbar 45
multisession--sbar 70
multisession--sbar 101
multisession--sbar ends up as 101
passed 1/5 multi-test-files-busy (1.110505 sec)
passed 2/5 multi-test-files-simple (0.344866 sec)
passed 3/5 multi-test-files-some-values (0.008406 sec)
Test multi-test-sqlite-busy backtrace:
make[3]: *** [lisp/emacs-lisp/multisession-tests.log] Error 134
[...]
SUMMARY OF TEST RESULTS
-----------------------
Files examined: 451
Ran 6654 tests, 5 failed to run, 6530 results as expected, 1
unexpected, 123 skipped
1 files did not finish:
lisp/emacs-lisp/multisession-tests.log
1 files contained unexpected results:
lisp/eshell/esh-var-tests.log
make[2]: *** [check-doit] Error 2
make[1]: *** [check] Error 2
make: *** [check] Error 2
In GNU Emacs 29.0.50 (build 3, x86_64-apple-darwin17.7.0, NS
appkit-1561.61 Version 10.13.6 (Build 17G14042)) of 2022-10-01 built on
SK-MacBook-Pro
Repository revision: 3faa508eba84a1983732099cbd3cc1eaad404158
Repository branch: master
Windowing system distributor 'Apple', version 10.3.1561
System Description: Mac OS X 10.13.6
Configured using:
'configure --with-native-compilation'
Configured features:
ACL GIF GLIB GMP GNUTLS JPEG JSON LCMS2 LIBXML2 MODULES NATIVE_COMP
NOTIFY KQUEUE NS PDUMPER PNG RSVG SQLITE3 THREADS TIFF
TOOLKIT_SCROLL_BARS WEBP XIM ZLIB
Important settings:
value of $LC_CTYPE: UTF-8
locale-coding-system: utf-8-unix
Major mode: Lisp Interaction
Minor modes in effect:
tooltip-mode: t
global-eldoc-mode: t
eldoc-mode: t
show-paren-mode: t
electric-indent-mode: t
mouse-wheel-mode: t
tool-bar-mode: t
menu-bar-mode: t
file-name-shadow-mode: t
global-font-lock-mode: t
font-lock-mode: t
blink-cursor-mode: t
line-number-mode: t
indent-tabs-mode: t
transient-mark-mode: t
auto-composition-mode: t
auto-encryption-mode: t
auto-compression-mode: t
Load-path shadows:
None found.
Features:
(shadow sort mail-extr emacsbug message mailcap yank-media puny dired
dired-loaddefs rfc822 mml mml-sec password-cache epa derived epg rfc6068
epg-config gnus-util text-property-search time-date mm-decode mm-bodies
mm-encode mail-parse rfc2231 mailabbrev gmm-utils mailheader sendmail
rfc2047 rfc2045 ietf-drums mm-util mail-prsvr mail-utils comp comp-cstr
warnings icons subr-x rx cl-seq cl-macs gv cl-extra help-mode
cl-loaddefs cl-lib bytecomp byte-compile cconv rmc iso-transl tooltip
eldoc paren electric uniquify ediff-hook vc-hooks lisp-float-type
elisp-mode mwheel term/ns-win ns-win ucs-normalize mule-util
term/common-win tool-bar dnd fontset image regexp-opt fringe
tabulated-list replace newcomment text-mode lisp-mode prog-mode register
page tab-bar menu-bar rfn-eshadow isearch easymenu timer select
scroll-bar mouse jit-lock font-lock syntax font-core term/tty-colors
frame minibuffer nadvice seq simple cl-generic indonesian philippine
cham georgian utf-8-lang misc-lang vietnamese tibetan thai tai-viet lao
korean japanese eucjp-ms cp51932 hebrew greek romanian slovak czech
european ethiopic indian cyrillic chinese composite emoji-zwj charscript
charprop case-table epa-hook jka-cmpr-hook help abbrev obarray oclosure
cl-preloaded button loaddefs faces cus-face macroexp files window
text-properties overlay sha1 md5 base64 format env code-pages mule
custom widget keymap hashtable-print-readable backquote threads kqueue
cocoa ns lcms2 multi-tty make-network-process native-compile emacs)
Memory information:
((conses 16 64035 6897)
(symbols 48 7032 0)
(strings 32 18188 3512)
(string-bytes 1 551337)
(vectors 16 14682)
(vector-slots 8 229100 11529)
(floats 8 26 25)
(intervals 56 206 0)
(buffers 1000 11))
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#58226
; Package
emacs
.
(Tue, 04 Oct 2022 11:28:01 GMT)
Full text and
rfc822 format available.
Message #8 received at 58226 <at> debbugs.gnu.org (full text, mbox):
Stefan Kangas <stefankangas <at> gmail.com> writes:
> passed 1/5 multi-test-files-busy (1.110505 sec)
> passed 2/5 multi-test-files-simple (0.344866 sec)
> passed 3/5 multi-test-files-some-values (0.008406 sec)
> Test multi-test-sqlite-busy backtrace:
> make[3]: *** [lisp/emacs-lisp/multisession-tests.log] Error 134
No backtrace? Did the testing Emacs segfault or something?
I've tried running "make check" myself now on Macos, and I see no
failures.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#58226
; Package
emacs
.
(Tue, 04 Oct 2022 11:29:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 58226 <at> debbugs.gnu.org (full text, mbox):
Lars Ingebrigtsen <larsi <at> gnus.org> writes:
> I've tried running "make check" myself now on Macos, and I see no
> failures.
This is with:
In GNU Emacs 29.0.50 (build 6, aarch64-apple-darwin21.6.0, NS
appkit-2113.60 Version 12.5.1 (Build 21G83)) of 2022-10-04 built on
emkay.local
Repository revision: 9fb0aaa1ce4ed0050d2e13552f078a563c8a20ed
Repository branch: master
System Description: macOS 12.5.1
Configured using:
'configure -C'
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#58226
; Package
emacs
.
(Tue, 04 Oct 2022 17:17:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 58226 <at> debbugs.gnu.org (full text, mbox):
Lars Ingebrigtsen <larsi <at> gnus.org> writes:
>
> Stefan Kangas <stefankangas <at> gmail.com> writes:
>
> > passed 1/5 multi-test-files-busy (1.110505 sec)
> > passed 2/5 multi-test-files-simple (0.344866 sec)
> > passed 3/5 multi-test-files-some-values (0.008406 sec)
> > Test multi-test-sqlite-busy backtrace:
> > make[3]: *** [lisp/emacs-lisp/multisession-tests.log] Error 134
>
> No backtrace? Did the testing Emacs segfault or something?
Indeed, there is a crash (SIGABRT). Emacs exits with this output:
Abort trap: 6
Running the tests interactively gives me the following output in the ert buffer:
Selector: t
Passed: 3
Failed: 2 (2 unexpected)
Skipped: 0
Total: 5/5
Started at: 2022-10-04 19:07:17+0200
Finished.
Finished at: 2022-10-04 19:07:20+0200
...FF
F multi-test-sqlite-busy
(error "near \"on\": syntax error")
F multi-test-sqlite-simple
(error "near \"on\": syntax error")
If I try to get the ELisp backtrace from ert with "b", Emacs crashes
with the below rather unhelpful backtrace. Any ideas for how to debug
further from here are welcome.
Thread 2 received signal SIGABRT, Aborted.
0x00007fff6d8a3b66 in ?? () from /usr/lib/system/libsystem_kernel.dylib
(gdb) bt
#0 0x00007fff6d8a3b66 in ?? () from /usr/lib/system/libsystem_kernel.dylib
#1 0x00007fff6da6e080 in pthread_kill () from
/usr/lib/system/libsystem_pthread.dylib
#2 0x00007fff6d7ff24d in __abort () from /usr/lib/system/libsystem_c.dylib
#3 0x0032000000000015 in ?? ()
#4 0x0000000000000000 in ?? ()
Lisp Backtrace:
"prin1" (0x6a00830)
0x70faa28 PVEC_COMPILED
"apply" (0x6a007e8)
0x5e4acb0 PVEC_COMPILED
0x5db99d0 PVEC_COMPILED
"apply" (0x6a00740)
0x5e4a198 PVEC_COMPILED
"apply" (0x6a006a0)
"cl-print-object" (0x6a00650)
0x70fac48 PVEC_COMPILED
"apply" (0x6a005f8)
0x5e4ac00 PVEC_COMPILED
0x5db99d0 PVEC_COMPILED
"apply" (0x6a00550)
0x5e4abb0 PVEC_COMPILED
"apply" (0x6a004b0)
"cl-print-object" (0x6a00460)
"cl-prin1" (0x6a00410)
"backtrace--print" (0x6a003b0)
"cl-print-to-string-with-limit" (0x6a00338)
"backtrace--print-to-string" (0x6a00298)
"backtrace--print-func-and-args" (0x6a00200)
"backtrace-print-frame" (0x6a00198)
"backtrace-print" (0x6a00110)
"ert-results-pop-to-backtrace-for-test-at-point" (0xefbfd420)
"funcall-interactively" (0xefbfd418)
"call-interactively" (0x6a00060)
"command-execute" (0xefbfeae0)
(gdb) bt full
#0 0x00007fff6d8a3b66 in ?? () from /usr/lib/system/libsystem_kernel.dylib
No symbol table info available.
#1 0x00007fff6da6e080 in pthread_kill () from
/usr/lib/system/libsystem_pthread.dylib
No symbol table info available.
#2 0x00007fff6d7ff24d in __abort () from /usr/lib/system/libsystem_c.dylib
No symbol table info available.
#3 0x0032000000000015 in ?? ()
No symbol table info available.
#4 0x0000000000000000 in ?? ()
No symbol table info available.
[New Thread 0x5117 of process 5165]
Lisp Backtrace:
"prin1" (0x6a00830)
0x70faa28 PVEC_COMPILED
"apply" (0x6a007e8)
0x5e4acb0 PVEC_COMPILED
0x5db99d0 PVEC_COMPILED
"apply" (0x6a00740)
0x5e4a198 PVEC_COMPILED
"apply" (0x6a006a0)
"cl-print-object" (0x6a00650)
0x70fac48 PVEC_COMPILED
"apply" (0x6a005f8)
0x5e4ac00 PVEC_COMPILED
0x5db99d0 PVEC_COMPILED
"apply" (0x6a00550)
0x5e4abb0 PVEC_COMPILED
"apply" (0x6a004b0)
"cl-print-object" (0x6a00460)
"cl-prin1" (0x6a00410)
"backtrace--print" (0x6a003b0)
"cl-print-to-string-with-limit" (0x6a00338)
"backtrace--print-to-string" (0x6a00298)
"backtrace--print-func-and-args" (0x6a00200)
"backtrace-print-frame" (0x6a00198)
"backtrace-print" (0x6a00110)
"ert-results-pop-to-backtrace-for-test-at-point" (0xefbfd420)
"funcall-interactively" (0xefbfd418)
"call-interactively" (0x6a00060)
"command-execute" (0xefbfeae0)
(gdb)
In GNU Emacs 29.0.50 (build 1, x86_64-apple-darwin17.7.0, NS
appkit-1561.61 Version 10.13.6 (Build 17G14042)) of 2022-10-04 built on
SK-MacBook-Pro
Repository revision: 0f1aabcbaa3d50b81bea7bedaa33c9351644c130
Repository branch: master
Windowing system distributor 'Apple', version 10.3.1561
System Description: Mac OS X 10.13.6
Configured using:
'configure --enable-checking=yes,glyphs --enable-check-lisp-object-type
'CFLAGS=-O0 -g3''
Configured features:
ACL GIF GLIB GMP GNUTLS JPEG JSON LCMS2 LIBXML2 MODULES NOTIFY KQUEUE NS
PDUMPER PNG RSVG SQLITE3 THREADS TIFF TOOLKIT_SCROLL_BARS WEBP XIM ZLIB
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#58226
; Package
emacs
.
(Tue, 04 Oct 2022 19:14:01 GMT)
Full text and
rfc822 format available.
Message #17 received at 58226 <at> debbugs.gnu.org (full text, mbox):
Stefan Kangas <stefankangas <at> gmail.com> writes:
> If I try to get the ELisp backtrace from ert with "b", Emacs crashes
> with the below rather unhelpful backtrace. Any ideas for how to debug
> further from here are welcome.
>
> Thread 2 received signal SIGABRT, Aborted.
> 0x00007fff6d8a3b66 in ?? () from /usr/lib/system/libsystem_kernel.dylib
> (gdb) bt
> #0 0x00007fff6d8a3b66 in ?? () from /usr/lib/system/libsystem_kernel.dylib
> #1 0x00007fff6da6e080 in pthread_kill () from
> /usr/lib/system/libsystem_pthread.dylib
> #2 0x00007fff6d7ff24d in __abort () from /usr/lib/system/libsystem_c.dylib
> #3 0x0032000000000015 in ?? ()
> #4 0x0000000000000000 in ?? ()
I'm almost completely blank on running the debugger on Macos, but Gerd
is an expert here -- Gerd, any advice?
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#58226
; Package
emacs
.
(Wed, 05 Oct 2022 04:50:02 GMT)
Full text and
rfc822 format available.
Message #20 received at 58226 <at> debbugs.gnu.org (full text, mbox):
Lars Ingebrigtsen <larsi <at> gnus.org> writes:
> Stefan Kangas <stefankangas <at> gmail.com> writes:
>
>> If I try to get the ELisp backtrace from ert with "b", Emacs crashes
>> with the below rather unhelpful backtrace. Any ideas for how to debug
>> further from here are welcome.
>>
>> Thread 2 received signal SIGABRT, Aborted.
>> 0x00007fff6d8a3b66 in ?? () from /usr/lib/system/libsystem_kernel.dylib
>> (gdb) bt
>> #0 0x00007fff6d8a3b66 in ?? () from /usr/lib/system/libsystem_kernel.dylib
>> #1 0x00007fff6da6e080 in pthread_kill () from
>> /usr/lib/system/libsystem_pthread.dylib
>> #2 0x00007fff6d7ff24d in __abort () from /usr/lib/system/libsystem_c.dylib
>> #3 0x0032000000000015 in ?? ()
>> #4 0x0000000000000000 in ?? ()
>
> I'm almost completely blank on running the debugger on Macos, but Gerd
> is an expert here
That's how quickly you get a bad reputation :-).
> -- Gerd, any advice?
It's to a degree similar to GDB. I'm using the cheat sheet from
https://lldb.llvm.org/use/map.html if in doubt. That's how experts do.
cd src
lldb --local-lldbinit emacs
You should see "Emacs support has been loaded". If not, you can load it
later with
command script import ../etc/emacs_lldb.py
To start Emacs
run <args...>
where <args...> are command-line options for Emacs. When back in lldb
because of the signal, use bt, up, down, and p as you would in GDB.
With emacs_lldb.py loaded, you can also use xbacktrace and xdebug_print.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#58226
; Package
emacs
.
(Wed, 05 Oct 2022 06:18:01 GMT)
Full text and
rfc822 format available.
Message #23 received at 58226 <at> debbugs.gnu.org (full text, mbox):
> Cc: 58226 <at> debbugs.gnu.org, Stefan Kangas <stefankangas <at> gmail.com>
> From: Gerd Möllmann <gerd.moellmann <at> gmail.com>
> Date: Wed, 05 Oct 2022 06:49:48 +0200
>
> > I'm almost completely blank on running the debugger on Macos, but Gerd
> > is an expert here
>
> That's how quickly you get a bad reputation :-).
It's in etc/DEBUG, isn't it?
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#58226
; Package
emacs
.
(Wed, 05 Oct 2022 07:01:02 GMT)
Full text and
rfc822 format available.
Message #26 received at 58226 <at> debbugs.gnu.org (full text, mbox):
Eli Zaretskii <eliz <at> gnu.org> writes:
> It's in etc/DEBUG, isn't it?
Ah, that's right, I forgot.
Reply sent
to
Stefan Kangas <stefankangas <at> gmail.com>
:
You have taken responsibility.
(Mon, 07 Nov 2022 10:24:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Stefan Kangas <stefankangas <at> gmail.com>
:
bug acknowledged by developer.
(Mon, 07 Nov 2022 10:24:02 GMT)
Full text and
rfc822 format available.
Message #31 received at 58226-done <at> debbugs.gnu.org (full text, mbox):
Stefan Kangas <stefankangas <at> gmail.com> writes:
> Failed test on macOS 10.13.6, see below output from "make check":
Unfortunately, I can no longer reproduce this after upgrading to macOS
12.6.1. I hope that someone in a position to reproduce this issue
will report it again if it has not already been solved. Closing this
bug for now.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Mon, 05 Dec 2022 12:24:04 GMT)
Full text and
rfc822 format available.
This bug report was last modified 1 year and 136 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.