You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@poi.apache.org by bu...@apache.org on 2003/06/02 11:59:42 UTC

DO NOT REPLY [Bug 20410] New: - NPE in org.apache.poi.hdf.extractor.Utils.convertBytesToShort

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20410>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20410

NPE in org.apache.poi.hdf.extractor.Utils.convertBytesToShort

           Summary: NPE in
                    org.apache.poi.hdf.extractor.Utils.convertBytesToShort
           Product: POI
           Version: 2.0-dev
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: HDF
        AssignedTo: poi-dev@jakarta.apache.org
        ReportedBy: mario@ops.co.at


Version: poi-src-2.0-pre1-20030517

When it comes to Utils.convertBytesToShort in 
org.apache.poi.hdf.extractor.StyleSheet.doCHPOperation, a NPE might be thrown 
in line 83 of Utils.


This happens, if varParam in "case 0x9" of doCHPOperation is null.

If i change this case 0x9 to

case 0x9:
    newCHP._fSpec = true;
    if (varParam == null)
    {
        newCHP._ftcSym = -1;
        newCHP._xchSym = -1;
    }
    else
    {
        newCHP._ftcSym = (short)Utils.convertBytesToShort(varParam, 0);
        newCHP._xchSym = (short)Utils.convertBytesToShort(varParam, 2);
    }
    break;

the document is parsed correctly, but i do not know, what side effects this 
could have