Bug 456765 - Entering an invalid breakpoint condition does not cause any error
Summary: Entering an invalid breakpoint condition does not cause any error
Status: RESOLVED FIXED
Alias: None
Product: TCF
Classification: Tools
Component: Agent (show other bugs)
Version: 1.1   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 1.3   Edit
Assignee: Project Inbox CLA
QA Contact: Eugene Tarassov CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-06 04:48 EST by Erwan Le Guillou CLA
Modified: 2015-06-16 03:17 EDT (History)
1 user (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 Erwan Le Guillou CLA 2015-01-06 04:48:47 EST 
Nothing happens because of the invalid breakpoint condition. The breakpoint is hit on each execution. Excepted behavior is that the user is warned that the condition cannot be evaluated and might be invalid and it is offered to edit the condition. 
To reproduce the problem, create a breakpoint with a non-sense condition, "aa+" for example.
Comment 1 Eugene Tarassov CLA 2015-01-09 17:32:50 EST 
I've added code to report condition evaluation error in the breakpoint status and in the breakpoint markers. In case of error, execution stops, breakpoint marker gets red error overlay, mouse hover reveals error message text.

Fixed.
Thanks!