Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 356600 - [crossfire] Add support for creating error problems in Eclipse from FB / Crossfire
Summary: [crossfire] Add support for creating error problems in Eclipse from FB / Cros...
Status: RESOLVED FIXED
Alias: None
Product: JSDT
Classification: WebTools
Component: Debug (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 3.4 M3   Edit
Assignee: Michael Rennie CLA
QA Contact: Michael Rennie CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 367806
  Show dependency tree
 
Reported: 2011-09-02 10:24 EDT by Michael Rennie CLA
Modified: 2012-01-03 19:45 EST (History)
4 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 Michael Rennie CLA 2011-09-02 10:24:48 EDT 
The Crossfire protocol has support for notifying clients when an error has been encountered (http://getfirebug.com/wiki/index.php/Crossfire_Protocol_Reference#onError) we should support handling this event in some way that the user can see / interact with in JSDT Debug.
Comment 1 Michael Rennie CLA 2011-10-06 13:50:27 EDT 
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.
Comment 2 Michael Rennie CLA 2011-10-06 14:14:37 EDT 
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.