On Thu, 23 May 2019 at 07:10, Timo Sintonen via D.gnu <d.gnu@puremagic.com> wrote: > > On Monday, 20 May 2019 at 19:12:54 UTC, Iain Buclaw wrote: > > On Mon, 20 May 2019 at 20:05, Timo Sintonen via D.gnu > > <d.gnu@puremagic.com> wrote: > >> > >> On Sunday, 19 May 2019 at 18:58:09 UTC, Iain Buclaw wrote: > >> > >> > > >> > What's the system compiler version you are using? I've > >> > tested with both gcc-9.1 and gcc-8.3, not able to reproduce. > >> > >> It is in the dump above (even two times ;) > >> > >> >> GNU D (GCC) version 9.1.0 (arm-eabi) > >> >> compiled by GNU C version 8.2.0, GMP version 6.1.2, > >> >> MPFR version > >> >> 4.0.1, MPC version 1.1.0, isl version none > >> > >> I'll try to update to 9.1 and test again > >> > > > > Or even just 8.3, I guess. > > I updated my system with the newest packages and even built gcc > 10 from master as host gcc. Still the same. I know I may have > something like old headers somewhere... I may test with a fresh > install at some point but for now I will just comment out the > failing code and continue. > > I think there is no point to try gdc 10 now. When will the new > frontend land into gcc master? >
Given the nature of the segfault your getting, I would expect that you'd get the same problem even if the sources were in D. It is _not_ normal for a module->importedFrom to be NULL or an invalid pointer. Something must have gone horribly awry in memory for that to happen. -- Iain
