Null pointer exception occurs when a ComException is created

[JohnRobPeter]

COMUtils.java

public static void checkRC(HRESULT hr) {
        checkRC(hr, (EXCEPINFO)null, (IntByReference)null);
    }

    public static void checkRC(HRESULT hr, EXCEPINFO pExcepInfo, IntByReference puArgErr) {
        if(FAILED(hr)) {
            String formatMessageFromHR = Kernel32Util.formatMessage(hr);
            throw new COMException(formatMessageFromHR, pExcepInfo, puArgErr);
        }
    }

while the first method calls the second with the second and third params set to null the second method creates a new ComException instance by passing a message got from Kernel32 and two null received as parameters to the constructor of ComException class.

COMException.java

    public COMException(String message, EXCEPINFO pExcepInfo, IntByReference puArgErr) {
        super(message + " (puArgErr=" + puArgErr.getValue() + ")");
        this.pExcepInfo = pExcepInfo;
        this.puArgErr = puArgErr;
    }

as the ComException class constructor has a call to super with a puArgErr.getValue as param we have a null pointer exception here because puArgErr from the code above is set to null

[dblock]

This is a good repro, turn it into a unit test and a fix?

[dblock]

Bump.

[matthiasblaesing]

This was fixed by: d6675fa