Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 368525 - Status of disabled breakpoint is empty
Summary: Status of disabled breakpoint is empty
Status: CLOSED FIXED
Alias: None
Product: TCF
Classification: Tools
Component: Debug (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 1.0.0   Edit
Assignee: Project Inbox CLA
QA Contact: Eugene Tarassov CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-13 05:07 EST by patrice guillemot CLA
Modified: 2013-06-05 05:42 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 patrice guillemot CLA 2012-01-13 05:07:20 EST 
Build Identifier: Version: Indigo Service Release 1 Build id: 20110916-0149

After disabling a BP, the status of the BP is empty. Only the properties are available. I think the status should be available regardless the BP state (enabled, disabled).

2012-01-10 17:17:13,271 : C 18 Breakpoints disable ["wrgdb:1"]
2012-01-10 17:17:13,274 : E None Breakpoints contextChanged [{"Enabled":false,"ID":"wrgdb:1","Location":"main"}]
2012-01-10 17:17:13,275 : R 18 None None 
2012-01-10 17:17:13,278 : E None Breakpoints status "wrgdb:1"

Reproducible: Always

Steps to Reproduce:
1. Set a BP
2. Get its status and properties
3. Disable the BP
4. Get its status and properties
Comment 1 Eugene Tarassov CLA 2012-01-13 13:59:48 EST 
Since the breakpoint is disabled, it is not planted, which is reflected by empty array of planting addresses in the status. I don't understand what is wrong with that.
Comment 2 patrice guillemot CLA 2012-01-17 07:46:40 EST 
I mis-understood the bp behaviour. I then close the Bug.