[FLEX-34751] Regression in fdb tool: VM is resumed if breakpoint can't be set

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Pending Closed
• Affects Version/s: Apache Flex 4.13.0, Apache Flex 4.14.0
• Fix Version/s: Apache Flex 4.15.0
• Component/s: FDB - Debugger
• Assignee: Frédéric THOMAS
• Reporter: Alexander Doroshko
• Created: 13/Feb/15 11:56
• Updated: 15/May/15 09:22
• Resolved: 15/May/15 03:01

Description

This regression appeared in Flex SDK 4.13. If fdb says "Breakpoint not set; no executable code at line ..." then VM must stay in suspended state, but it resumes. As a result IntelliJ IDEA users who have at least one breakpoint at the line without executable code can't debug the app at all.

To reproduce:
1. Take any simple AS application, for example, attached Main.as and compiled Main.swf
2. In Terminal run [Flex SDK]/bin/fdb, type 'run' and Enter
3. Launch Main.swf
4. Debugger will attach and fdb console will suggest to set breakpoints. Type 'break Main.as:1' and Enter
5. fdb says 'Breakpoint not set; no executable code at line 1 of Main.as#1', VM resumes, application runs. The problem is that the client has no chance to set other breakpoints after that.

Expected result is that after saying 'Breakpoint not set...' VM remains suspended, fdb prints its prompt (fdb), so client is able to enter more 'break' commands.