Never mind, that was a coincidence. All of the errors are on lines calling
java:: something, or calling _Jv_ something.
On Sat, 21 May 2022 at 17:12, Zopolis0 <creatorsmithmdt@xxxxxxxxx> wrote:
> Running with make -k reveals that all the errors are segfaults, and all of
> them are on return new or throw new statements. One such error is on the
> return new FileOutputStream (ch); line in natVMChannels.cc:
>
> FileOutputStream*
> VMChannels::newOutputStream(FileChannelImpl* ch)
> {
> // Needs to be native to bypass Java access protection.
> return new FileOutputStream (ch);
> }
>
> Given that this does not seem like the kind of code to generate a
> segfault, I think there is a different issue here.
>
>
> On Thu, May 19, 2022 at 10:22 PM Zopolis0 <creatorsmithmdt@xxxxxxxxx>
> wrote:
>
>> It's the same implementation from when it was removed, unless you mean
>> code outside of gcc/java and libjava, which in that case I could have made
>> an error copying it in or modernising it.
>>
>> On Thu, May 19, 2022 at 8:47 PM Florian Weimer <fweimer@xxxxxxxxxx>
>> wrote:
>>
>>> * Zopolis:
>>>
>>> > ../../../../gcj/libjava/prims.cc:182:23: internal compiler error:
>>> > Segmentation fault
>>> > 182 | = new java::lang::NullPointerException;
>>> > | ^~~~~~~~~~~~~~~~~~~~
>>>
>>> This is likely a bug in the CNI implementation, specific to your GCJ
>>> port. Allocation of CNI classes is different from regular C++ classes.
>>>
>>> Thanks,
>>> Florian
>>>
>>>
