making sense of crashes in build logs

[Thorsten Glaser]

Hi,

how do I make sense of crashes in buildd logs, such as:
https://buildd.debian.org/status/fetch.php?pkg=openjdk-8&arch=m68k&ver=8u402-ga-6&stamp=1711506075&raw=1

I saw…
#  Internal Error (os_linux_zero.cpp:254), pid=830846, tid=0x3f629440
… and thought, yay, we can look at where the segfault is,
but that address is the generic signal handler ☹

Is there a way to get a backtrace into these messages?

Building locally in a VM would take… over a week, I think,
and gdb is also currently not very usable on m68k, at least
it wasn’t when I was trying to debug a different crash in a
different software…

Help with m68k is welcome in general; the last version that
built was 8u171-b11, the first to fail was 8u181-b13 and all
others since. Some patch probably needs updating or something.

Thanks,
//mirabilos
-- 
Infrastrukturexperte • Qvest Digital AG
Am Dickobskreuz 10, D-53121 Bonn • https://www.qvest-digital.com/
Telephon +49 228 54881-393 • Fax: +49 228 54881-235
HRB AG Bonn 18196 • USt-ID (VAT): DE274355441
Vorstand: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
Vorsitzender Aufsichtsrat: Peter Nöthen