making sense of crashes in build logs

[Thorsten Glaser]

Hi David,

> If there is no backtrace in the hs_err log then it is because the VM was not in
> a state where stack walking (as per the port) was possible.

ok.

> If there was a core file then you may be able to debug that.

Yes, "may"… I have not had much luck with gdb on m68k recently,
sadly, but I’ll ask other people to have a look into *that*.

> Otherwise if this crashed during the build you should be able to run
> the crashing JVM directly and potentially debug things further that
> way i.e.
>
>> configure:5339: checking if the VM and compiler work together
>
> Try running the underlying command directly.

It did crash during the build, but on one of the "fast" qemu-user-
based buildds, which means I do not have access to the build chroot.

I can build it on my Atari VM myself, but it takes about a week at
least to get to that place…

> Is this running under an emulator? The build version is for m68k but
> the crash log shows an x86 machine.

Yes, qemu-user here.

Thanks nevertheless,
//mirabilos
-- 
15:41⎜<Lo-lan-do:#fusionforge> Somebody write a testsuite for helloworld :-)