Finished part 1 of the Wayland McWayface tutorial of Drew DeVault - Issue with spi toolprovider interface and jextract

[Mark Hammons]

I gave it a shot, and changed my setProperty to a getProperty to make 
sure the debug flag was set and still no helpful debug information. This 
gets printed out whenever I run sbt, so maybe it's related?

error: error while loading String, class file 
'/modules/java.base/java/lang/String.class' is broken
(class java.lang.NullPointerException/null)

On 2/25/19 3:11 PM, Mark Hammons wrote:
> I will do this when I return home tonight.
>
> On 25/02/2019 12:37, Maurizio Cimadamore wrote:
>>
>> On 25/02/2019 00:40, Mark Hammons wrote:
>>> So at least I know the command is failing, but still no output as to 
>>> why. 
>>
>> Error code 4 means jextract failed with some runtime exception - but 
>> the "jextract.debug" option should print the exception message:
>>
>> ```
>> ctx.err.println(re.getMessage());
>> if (Main.DEBUG) {
>>   re.printStackTrace(ctx.err);
>> }
>> return RUNTIME_ERROR;
>> ```
>>
>> I'm not sure setting the property the way you do is the right way to 
>> go. The property is cached in a static field:
>>
>> ```
>> public static final boolean DEBUG = 
>> Boolean.getBoolean("jextract.debug");
>> ```
>>
>> So you are basically depending on the order in which classes are 
>> loaded/initialized here. Can you try to pass -Djextract.debug to the 
>> VM directly instead of doing it from the program? (not 100% sure that 
>> is why you are getting no output, but let's try to remove as many 
>> accidental factors as possible).
>>
>>
>> Maurizio
>>
>>
>>
>