Bugzilla – Full Text Bug Listing
| Summary: | xgconf: javascript var gets confused with config param and causes NPE | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Technology] RTSC | Reporter: | Jon Rowlands <rowlands> | ||||
| Component: | Tools | Assignee: | Jon Rowlands <rowlands> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P1 | CC: | amitm, d-russo | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | target:3.20.01 | ||||||
| Attachments: |
|
||||||
Fixed in xdcconfig-g23 in ScriptNode.java Verified in xdcprod-m48. Created a grace project. Added the two lines of configuration script in the attachment. The configuration was validated successfully without any errors. Shipped in XDCtools 3.20.01 |
Created attachment 170354 [details] Config file to reproduct If the name of a javascript variable matches the name of some config parameter, then XGCONF can throw a null pointer exception whenever the script is validated. The attached .cfg file illustrates. The instance is given the javascript var name "clock". The module Clock2xx has a config paramater also named "clock", which points to the instance. XGCONF incorrectly deduces that the clock is an instance of Clock2xx module, instead of just a referent of a config param. Found in XDCtools 3.20.