Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 340702

Summary: Breakpoint condition sent to crossfire regardless of condition enabled state
Product: [WebTools] JSDT Reporter: Michael Rennie <Michael_Rennie>
Component: DebugAssignee: Project Inbox <jsdt.debug-inbox>
Status: RESOLVED WONTFIX QA Contact: Michael Rennie <Michael_Rennie>
Severity: normal    
Priority: P3 CC: thatnitind
Version: 3.3   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description Michael Rennie CLA 2011-03-22 15:37:08 EDT
code from HEAD

If you create a breakpoint, add a condition, then remove the condition, the saved condition from the IDE is always sent over the wire in the "condition" value.

Consider the following crossfire trace:

WRITE PACKET: Content-Length:233\r\n\r\n{"arguments":{"enabled":true,"condition":"google != 'undefined'","location":{"line":2,"url":"http:\/\/www.google.ca\/\/event\/seq\/1"},"type":"line"},"context_id":"xf0.3::2278098","command":"setbreakpoint","seq":156,"type":"request"}\r\n

I got this trace when I re-connected the debugger and it tried to install the breakpoint in Firebug. The problem is that the breakpoint in the IDE has a condition *but* the condition is not enabled. In that case I would not expect to see the condition to be sent to Firebug.
Comment 1 Michael Rennie CLA 2013-11-12 13:59:05 EST
In a future release of Firebug, Crossfire support will be dropped completely in favour or JSD2 and RDP, as such no more bugs will be fixed for the Crossfire support.

See:
1. https://wiki.mozilla.org/Firebug/WeeklyUpdates/2013-11-05#Crossfire
2. https://getfirebug.com/wiki/index.php/JSD2_Adoption
3. https://wiki.mozilla.org/Debugger