On 23/06/20 11:11, Nadav Amit wrote: >> I'm not sure why it starts failing now, the bug is unrelated and I see >> the same compiler output even before. > I encountered the same problem on my (weird) setup, and made some initial > triage. Apparently, it is only the #DE that causes the mess. As the #DE uses > vector number 0, and the IDT base is 0, it hints that the data in address 0 > is corrupted. > > I presume there is somewhere a rogue store into a NULL pointer during the > 32-bit setup. But I do not know where. Thanks, that is certainly going to be helpful. Paolo
