This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 197119 - NullPointerException: The null file object parameter cannot be null
Summary: NullPointerException: The null file object parameter cannot be null
Status: RESOLVED DUPLICATE of bug 196269
Alias: None
Product: cnd
Classification: Unclassified
Component: Code Model (show other bugs)
Version: 7.0
Hardware: All All
: P3 normal (vote)
Assignee: issues@cnd
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-26 19:36 UTC by Exceptions Reporter
Modified: 2011-03-26 20:09 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 177874

Attachments
stacktrace (3.90 KB, text/plain)
2011-03-26 19:36 UTC, Exceptions Reporter 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Exceptions Reporter 2011-03-26 19:36:28 UTC 
This issue was reported manually by vv159170.
It already has 1 duplicates 


Build: NetBeans IDE 7.0 Beta 2 (Build 201102140001)
VM: Java HotSpot(TM) Client VM, 19.1-b02, Java(TM) SE Runtime Environment, 1.6.0_24-b07
OS: Linux

Stacktrace: 
java.lang.NullPointerException: The null file object parameter cannot be null
   at org.openide.util.Parameters.notNull(Parameters.java:89)
   at org.netbeans.modules.cnd.modelimpl.platform.ModelSupport.createFileBuffer(ModelSupport.java:421)
   at org.netbeans.modules.cnd.modelimpl.parser.apt.APTSelfWalker.include(APTSelfWalker.java:70)
   at org.netbeans.modules.cnd.apt.support.APTAbstractWalker.includeImpl(APTAbstractWalker.java:151)
   at org.netbeans.modules.cnd.apt.support.APTAbstractWalker.onInclude(APTAbstractWalker.java:113)
   at org.netbeans.modules.cnd.apt.support.APTWalker.onAPT(APTWalker.java:223)
Comment 1 Exceptions Reporter 2011-03-26 19:36:33 UTC 
Created attachment 107304 [details]
stacktrace
Comment 2 Vladimir Voskresensky 2011-03-26 20:09:20 UTC 

*** This bug has been marked as a duplicate of bug 196269 ***