| Summary: | XDCtool error parser should filter out stack traceback error | ||
|---|---|---|---|
| Product: | [Technology] RTSC | Reporter: | Dave Russo <d-russo> |
| Component: | Tools | Assignee: | Amit Mookerjee <amitm> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P1 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | target:3.21 | ||
Fixed in xdceclipse-h00 created a config script with the line
throw new Error("foo");
verified that the error parser in xdctool 3.21.00.51 reported the error just once.
Shipped in XDCtools 3.21. Shipped in XDCtools 3.21 |
Currently (3.20.x), the XDCtools error parser treats the following as 4(!) error rather than the one that it really is: js: "C:/users/dr/tmp/ccs4_2_beta_test/tmp/main.cfg", line 14: Error: foo "./package/cfg/main_p430.cfg", line 490 "./package/cfg/main_p430.cfg", line 545 "./package/cfg/main_p430.cfg", line 477 The error parser shoult report a single error on line 14 of C:/users/dr/tmp/ccs4_2_beta_test/tmp/main.cfg with a description of "foo".