Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 318113 - xgconf: xdc.lookup and config param name match causes NPE
Summary: xgconf: xdc.lookup and config param name match causes NPE
Status: ASSIGNED
Alias: None
Product: RTSC
Classification: Technology
Component: Tools (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P1 normal (vote)
Target Milestone: ---   Edit
Assignee: Jon Rowlands CLA
QA Contact:
URL:
Whiteboard: target: 3.40
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-27 03:09 EDT by Jon Rowlands CLA
Modified: 2014-02-26 00:27 EST (History)
2 users (show)

See Also:

Attachments
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 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".