Bugzilla – Full Text Bug Listing
| Summary: | logFatal doesn't work in meta functions | ||
|---|---|---|---|
| Product: | [Technology] RTSC | Reporter: | Shreyas Prasad <shreyasp> |
| Component: | Platforms | Assignee: | Sasha Slijepcevic <sascha> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | d-russo |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
- fixed in xdc-w14 The cause of the bug was that a user's script was executing outside of a try-catch block in runStringCfg in xdc/cfg/Main.xs. That block was catching an error thrown by $logFatal, and then displaying previously accumulated errors and warnings. Now, a user's script is inside the block. Previously, this was a problem for xgconf when xgconf invoked runStringCfg directly, without going through main(). Jon R. will check if such a problem still exists and try to solve it inside xgconf. closing "ancient" resolved bugs |
Build Identifier: xdctools_3_20_05_69_eng Are we allowed to call this.$logFatal() from a meta function? I’ve observed that doing so results in some strange output when hitting the logError from the meta function. I have this in my meta function: this.$logFatal("The device (" + Program.cpu.deviceName + ") isn't supported by Notify", this); And I get this when hitting this statement: js: "Settings.xs", line 491: Error: xdc.fatal.error instead of the error message. Reproducible: Always Steps to Reproduce: See 'details' section