* bug#51131: 29.0.50; Segfault in ERT test
@ 2021-10-11 6:07 Helmut Eller
2021-10-11 9:14 ` Lars Ingebrigtsen
0 siblings, 1 reply; 4+ messages in thread
From: Helmut Eller @ 2021-10-11 6:07 UTC (permalink / raw)
To: 51131
Emacs receives a segmentation fault when executing this file:
(ert-deftest segfault ()
(let ((debug-on-error nil))
(error "foo")))
with
emacs -Q -batch -l /tmp/test.el -f ert-run-tests-batch-and-exit
The backtrace in gdb is very long and seems to show an endless recursion
in Fsignal:
gdb -q --args emacs -Q -batch -l /tmp/test.el -f ert-run-tests-batch-and-exit
Reading symbols from emacs...
(gdb) r
Starting program: /home/helmut/bin/emacs -Q -batch -l /tmp/test.el -f ert-run-tests-batch-and-exit
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff228c700 (LWP 10498)]
Running 1 tests (2021-10-11 08:04:00+0200, selector ‘t’)
Thread 1 "emacs" received signal SIGSEGV, Segmentation fault.
0x00005555556ff741 in signal_or_quit (error_symbol=0xfc60,
data=0x555556079a53, keyboard_quit=false) at eval.c:1768
1768 {
(gdb) bt 20
#0 0x00005555556ff741 in signal_or_quit
(error_symbol=0xfc60, data=0x555556079a53, keyboard_quit=false)
at eval.c:1768
#1 0x0000555555599594 in Fsignal (error_symbol=<optimized out>,
error_symbol@entry=0xfc60, data=<optimized out>) at eval.c:1750
#2 0x000055555559974d in xsignal (data=<optimized out>, error_symbol=0xfc60)
at lisp.h:4152
#3 xsignal2
(error_symbol=error_symbol@entry=0xfc60, arg1=arg1@entry=0xdb00, arg2=arg2@entry=0x555555dc33a5) at eval.c:1913
#4 0x00005555555987f0 in wrong_type_argument
(predicate=predicate@entry=0xdb00, value=value@entry=0x555555dc33a5)
at data.c:143
#5 0x000055555559985e in CHECK_TYPE (x=0x555555dc33a5, predicate=0xdb00, ok=0)
at lisp.h:759
#6 CHECK_SYMBOL (x=0x555555dc33a5) at lisp.h:1028
#7 specbind (symbol=0x555555dc33a5, value=<optimized out>) at eval.c:3542
#8 0x00005555556ffbf5 in signal_or_quit
(error_symbol=<optimized out>, data=0x555556079a23, keyboard_quit=<optimized out>) at lisp.h:1002
#9 0x0000555555599594 in Fsignal (error_symbol=<optimized out>,
error_symbol@entry=0xfc60, data=<optimized out>) at eval.c:1750
#10 0x000055555559974d in xsignal (data=<optimized out>, error_symbol=0xfc60)
at lisp.h:4152
#11 xsignal2
(error_symbol=error_symbol@entry=0xfc60, arg1=arg1@entry=0xdb00, arg2=arg2@entry=0x555555dc33a5) at eval.c:1913
#12 0x00005555555987f0 in wrong_type_argument
(predicate=predicate@entry=0xdb00, value=value@entry=0x555555dc33a5)
at data.c:143
#13 0x000055555559985e in CHECK_TYPE (x=0x555555dc33a5, predicate=0xdb00, ok=0)
at lisp.h:759
#14 CHECK_SYMBOL (x=0x555555dc33a5) at lisp.h:1028
#15 specbind (symbol=0x555555dc33a5, value=<optimized out>) at eval.c:3542
#16 0x00005555556ffbf5 in signal_or_quit
(error_symbol=<optimized out>, data=0x5555560799f3, keyboard_quit=<optimized out>) at lisp.h:1002
#17 0x0000555555599594 in Fsignal (error_symbol=<optimized out>,
error_symbol@entry=0xfc60, data=<optimized out>) at eval.c:1750
#18 0x000055555559974d in xsignal (data=<optimized out>, error_symbol=0xfc60)
at lisp.h:4152
#19 xsignal2
(error_symbol=error_symbol@entry=0xfc60, arg1=arg1@entry=0xdb00, arg2=arg2@entry=0x555555dc33a5) at eval.c:1913
(More stack frames follow...)
(gdb)
Helmut
In GNU Emacs 29.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.24, cairo version 1.16.0)
of 2021-10-06 built on caladan
Repository revision: 597b6deb294ace9178c8927f83ec08b92597b347
Repository branch: master
Windowing system distributor 'The X.Org Foundation', version 11.0.12011000
System Description: Debian GNU/Linux 11 (bullseye)
Configured using:
'configure --with-xpm=ifavailable --with-jpeg=ifavailable
--with-gif=ifavailable --with-tiff=ifavailable'
Configured features:
CAIRO DBUS FREETYPE GLIB GMP GNUTLS GSETTINGS HARFBUZZ LIBSELINUX
LIBSYSTEMD LIBXML2 MODULES NOTIFY INOTIFY PDUMPER PNG SECCOMP SOUND
THREADS TOOLKIT_SCROLL_BARS X11 XDBE XIM GTK3 ZLIB
Important settings:
value of $LANG: C.UTF-8
locale-coding-system: utf-8-unix
^ permalink raw reply [flat|nested] 4+ messages in thread
* bug#51131: 29.0.50; Segfault in ERT test
2021-10-11 6:07 bug#51131: 29.0.50; Segfault in ERT test Helmut Eller
@ 2021-10-11 9:14 ` Lars Ingebrigtsen
2021-10-11 12:39 ` Philipp Stephani
0 siblings, 1 reply; 4+ messages in thread
From: Lars Ingebrigtsen @ 2021-10-11 9:14 UTC (permalink / raw)
To: Helmut Eller; +Cc: 51131
Helmut Eller <eller.helmut@gmail.com> writes:
> Emacs receives a segmentation fault when executing this file:
>
> (ert-deftest segfault ()
> (let ((debug-on-error nil))
> (error "foo")))
>
> with
>
> emacs -Q -batch -l /tmp/test.el -f ert-run-tests-batch-and-exit
This should now be fixed in emacs-28 (and on the trunk once the fix is
merged).
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
^ permalink raw reply [flat|nested] 4+ messages in thread
* bug#51131: 29.0.50; Segfault in ERT test
2021-10-11 9:14 ` Lars Ingebrigtsen
@ 2021-10-11 12:39 ` Philipp Stephani
2021-10-11 12:56 ` Lars Ingebrigtsen
0 siblings, 1 reply; 4+ messages in thread
From: Philipp Stephani @ 2021-10-11 12:39 UTC (permalink / raw)
To: Lars Ingebrigtsen; +Cc: 51131, Helmut Eller
Am Mo., 11. Okt. 2021 um 11:16 Uhr schrieb Lars Ingebrigtsen <larsi@gnus.org>:
>
> Helmut Eller <eller.helmut@gmail.com> writes:
>
> > Emacs receives a segmentation fault when executing this file:
> >
> > (ert-deftest segfault ()
> > (let ((debug-on-error nil))
> > (error "foo")))
> >
> > with
> >
> > emacs -Q -batch -l /tmp/test.el -f ert-run-tests-batch-and-exit
>
> This should now be fixed in emacs-28 (and on the trunk once the fix is
> merged).
I don't think that's the right fix. I added backtrace support in batch
mode primarily for unit tests running on CI systems; this is exactly
the situation where I want backtrace-on-error-noninteractive to be t.
Can we revert commit 07edc28bdbfeeaeb1008b4fe21bfda586feae562 and find
a better way?
^ permalink raw reply [flat|nested] 4+ messages in thread
* bug#51131: 29.0.50; Segfault in ERT test
2021-10-11 12:39 ` Philipp Stephani
@ 2021-10-11 12:56 ` Lars Ingebrigtsen
0 siblings, 0 replies; 4+ messages in thread
From: Lars Ingebrigtsen @ 2021-10-11 12:56 UTC (permalink / raw)
To: Philipp Stephani; +Cc: 51131, Helmut Eller
Philipp Stephani <p.stephani2@gmail.com> writes:
> I don't think that's the right fix. I added backtrace support in batch
> mode primarily for unit tests running on CI systems; this is exactly
> the situation where I want backtrace-on-error-noninteractive to be t.
> Can we revert commit 07edc28bdbfeeaeb1008b4fe21bfda586feae562 and find
> a better way?
ert wants to collect the backtrace, but the test itself subverted that
(by setting debug-on-error to nil and then having an error in the test).
I don't see why Emacs should output a backtrace inside a test like that.
But Emacs will still output
Error running tests
backtrace()
#f(compiled-function () #<bytecode -0x1fecd686855e18f0>)()
ert-run-tests-batch-and-exit()
command-line-1(("-l" "/tmp/test.el" "-f" "ert-run-tests-batch-and-exit"))
command-line()
normal-top-level()
at the end.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2021-10-11 12:56 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2021-10-11 6:07 bug#51131: 29.0.50; Segfault in ERT test Helmut Eller
2021-10-11 9:14 ` Lars Ingebrigtsen
2021-10-11 12:39 ` Philipp Stephani
2021-10-11 12:56 ` Lars Ingebrigtsen
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.