Dropping gives instant crash in latest 5/28 experimental

It is very consistent. Every drop of an item causes a crash. I got a gdb backtrace. The virtual base address is 0x0000555555554000. Here’s the latest output.

cataclysm-tiles: src/optional.h:46: const T& cata::optional<T>::get() const [with T = vpart_reference]: Assertion `full' failed.

Thread 1 "cataclysm-tiles" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
49      ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
#1  0x00007ffff78b9864 in __GI_abort () at abort.c:79
#2  0x00007ffff78b9749 in __assert_fail_base (fmt=0x7ffff7a45458 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x5555562585d5 "full", file=0x555556200bcd "src/optional.h", line=46, function=<optimized out>) at assert.c:92
#3  0x00007ffff78cba96 in __GI___assert_fail (assertion=0x5555562585d5 "full", file=0x555556200bcd "src/optional.h", line=46, function=0x55555620b8c2 "const T& cata::optional<T>::get() const [with T = vpart_reference]") at assert.c:101
#4  0x00005555557b54bc in  ()
#5  0x00005555558a3ddc in  ()
#6  0x0000555555a43cc4 in  ()
#7  0x0000555555ace821 in  ()
#8  0x0000555555a767ef in  ()
#9  0x000055555565fe64 in main ()

Have not determined whether this is specific to one save yet. I could upload a save if people are interested.

EDIT: Does not seem to be specific to any one save.

This was already fixed in build 2021-05-28-2349 (which is the latest build for 5/28).

Ah ok. Is this available on the experimental releases page?

Not yet, I think. But you can grab it (or an even more recent one) on the GitHub release page.

1 Like