Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 370234 - Missing Breakpoints status event on second disable command
Summary: Missing Breakpoints status event on second disable command
Status: CLOSED FIXED
Alias: None
Product: TCF
Classification: Tools
Component: Agent (show other bugs)
Version: 1.0   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-31 11:01 EST by Scott Tepavich CLA
Modified: 2013-06-05 05:42 EDT (History)
2 users (show)

See Also:


Attachments
Example communication log. (10.82 KB, application/octet-stream)
2012-01-31 11:01 EST, Scott Tepavich CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Scott Tepavich CLA 2012-01-31 11:01:50 EST
Created attachment 210318 [details]
Example communication log.

The client is not receiving a Breakpoints status event, when processing an enable/disable test on a function/expression breakpoint.  Note that the correct sequence of events are generated for source line breakpoints, when processing the same sequence of commands (e.g. this issue seems specific to function breakpoints)...

Steps to reproduce:

1.) Begin debugging a simple linux application.
2.) Set a function breakpoint (in this case main).
3.) In the UI, disable the function breakpoint.
    a.) Note the sequence of events from the agent.
4.) In the UI, enable the function breakpoint.
    a.) Note the sequence of events from the agent.
5.) In the UI, disable the function breakpoint.

At this point the Breakpoints status event is missing.
Comment 1 Eugene Tarassov CLA 2012-02-01 14:20:46 EST
I cannot reproduce.

In the log, I see a command with weird/invalid arguments:
379.973 Out: C 60 Breakpoints change ... Line:-1,Column:-1 ...

Please, verify that the issue is reproducible with original code from eclipse.org repository - it looks like you are running some derivation.
Comment 2 Scott Tepavich CLA 2012-02-01 16:31:01 EST
Updated the client to help address this issue.