On Wed, 14 Apr 2021 11:59:43 +0200 =?UTF-8?Q?Bernhard_=c3=9cbelacker?= <bernha...@mailbox.org> wrote: > Hello Ray, > from the "Code:" line you supplied I think the segfault happens > in create_cache_trans at ../src/mesa/state_tracker/st_cb_bitmap.c:402. > > https://sources.debian.org/src/mesa/20.3.5-1/src/mesa/state_tracker/st_cb_bitmap.c/#L402 > > > But I guess this information is not enough for the maintiner, > to find out what inputs causing the segfault in this function. > > Maybe you could install systemd-coredump and deliver the > output of 'journalctl --no-pager' following the last segfault line, > that appears in dmesg too. > > More details are in this link: https://wiki.debian.org/HowToGetABacktrace
Warning, a coredump from this system would be immense. Or, well anyway pretty darn large. The machine has over 64G of RAM memory installed and openuniverse seems to expand to fill available space. I could make a VM with artificially small memory to produce a more manageable coredump, but I wonder whether a VM environment would tickle the spot that provokes this bug. Bear
