[tcf-dev] Breakpoints Sharing

[Frederic Leger <frederic.leger@xxxxxxxxxxxxx>]

All,

we have the same kind of problem with sharing breakpoints than Khaled,
and have started to think about it. Wind Rive is already starting a
prototype for it.

We would like your advice here, to make sure we are doing what is
appropriate, and to make sure we are not forgetting something.

We propose to:

  - Add the -DENABLE_BreakpointsSharing support to the agent build.

  - If enabled, the Breakpoints.getCapabilities() would return the
    "BreakpointsSharing":True capability.

  - When a breakpoint is created (Breakpoints.add()), it is up to the
    creator client to set the breakpoint "Shared" property to either
    True or False (default would be False from an agent point of view).

  - When another client wants to modify (Breakpoints.set()) the
    breakpoint, if the "Shared" property of the breakpoint is True:

      + the following properties may be changed (according to
        capabilities too):

	* "AccessMode"
	* "Action"
	* "BreakpointType"
	* "Column"
	* "Condition"
	* "ContextIds"
	* "ContextNames"
	* "ContextQuery"
	* "Enabled"
	* "EventArgs"
	* "EventType"
	* "ExecPaths"
	* "File"
	* "FileLine"
	* "IgnoreCount"
	* "LineOffset"
	* "Location"
	* "Mask"
	* "Pattern"
	* "SkipPrologue"
	* "StopGroup"
	* "Temporary"
	* "Time"
	* "TimeScale"
	* "TimeUnits"

      + the following properties may NOT be changed:

	* "ClientData" - This is typically Eclipse data which may break
                         the breakpoints view if changed.
	* "ID"
	* "Size"
	* "Shared"

On a workflow point of view:

  - When the breakpoint creator exits, all its breakpoints are removed,
    even if "set()" by another client.
  - We are not sure if a breakpoint may be removed by another client
    than the creator ... is it useful ?

Comments or ideas are welcome, we are starting the prototype now :)

Hope this helps

DERF

PS : we plan on doing the same for pathmaps later on.