PR# 16618 Setting conditional breakpoint sometimes sets unconditional breakpoint

Problem Report Summary

Submitter: prestoat2000

Category: Debugger

Priority: Medium

Date: 2010/02/05

Class: Bug

Severity: Serious

Number: 16618

Release: 6.5.81777

Confidential: No

Status: Closed

Responsible: jfiat_es

Environment: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.9.0.10) Gecko/2009042715 Firefox/3.0.10 Solaris 10 on SPARC

Synopsis: Setting conditional breakpoint sometimes sets unconditional breakpoint

Description

Setting a conditional breakpoint sometimes sets an unconditional breakpoint instead.
This seems to happen after an unconditional breakpoint is set on  a stop point
and then removed.

To Reproduce

Start estudio and compile root class TEST with empty creation procedure `make'.
Target Feature tool to {TEST}.make.
Left-click on only breakable point in `make' to set breakpoint, then left-click
   again to remove breakpoint.
Right-click on the only breakable point in `make' and select Set Conditional Breakpoint.
Enter condition`False' and click OK.
Estudio enters unconditional breakpoint, instead of conditional breakpoint.
Right-click on breakpoint - condition is empty.
Click on Run.  Stops at breakpoint (ignores condition, which didn't get entered).

Problem Report Interactions

From:jfiat_es Date:2010/02/15 Status: Closed Download

Fixed in revision rev#82341