| Summary: | [crossfire] Add support for creating error problems in Eclipse from FB / Crossfire | ||
|---|---|---|---|
| Product: | [WebTools] JSDT | Reporter: | Michael Rennie <Michael_Rennie> |
| Component: | Debug | Assignee: | Michael Rennie <Michael_Rennie> |
| Status: | RESOLVED FIXED | QA Contact: | Michael Rennie <Michael_Rennie> |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | grant_gayed, hernanpepe, jzhang, thatnitind |
| Version: | unspecified | ||
| Target Milestone: | 3.4 M3 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 367806 | ||
|
Description
Michael Rennie
I committed a fix to HEAD that provides the hooks in the event queue to process the onError event and simply dump it out to the error log. It would be nice if there was a way to show the entire stacktrace for the onError event, but currently the Crossfire extension tries to serialize the data as object references, which we cannot as details for when the debugger (Firebug) is not suspended. I opened http://code.google.com/p/fbug/issues/detail?id=4895 against crossfire to make the onError event a bit more sane. Marking fixed. Any polish work can be requested in their own bugs. |