Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 318113

Summary: xgconf: xdc.lookup and config param name match causes NPE
Product: [Technology] RTSC Reporter: Jon Rowlands <rowlands>
Component: ToolsAssignee: Jon Rowlands <rowlands>
Status: ASSIGNED --- QA Contact:
Severity: normal    
Priority: P1 CC: d-russo, dfriedland
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: target: 3.40

Description Jon Rowlands CLA 2010-06-27 03:09:08 EDT
For instances initialized in config script using xdc.lookup(),
can get a null pointer exception while the script is validating,
before spec info is available.

Seems to be restricted to the case when the instance is assigned
to a config param and a JavaScript variable with the same name.
Seems to be restricted to XDCtools 3.21 / xdcconfig-h series due
to lazy initialization of config params.

To reproduce, use Radio product access point example, and make
sure "clock" register-object instance is assigned to a JavaScript
variable also named "clock".