Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 368410

Summary:	Source line BP scoped only to current selected thread
Product:	[Tools] TCF	Reporter:	Scott Tepavich <scott.tepavich>
Component:	Debug	Assignee:	Project Inbox <tcf.debug-inbox>
Status:	NEW ---	QA Contact:	Eugene Tarassov <eugene>
Severity:	normal
Priority:	P3	CC:	cdtdoug, scott.tepavich
Version:	1.0
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Scott Tepavich

2012-01-12 01:00:38 EST

The default behavior is not consistant between address breakpoints and source line breakpoints.

Example:

1.) Connect to a target.
2.) Select a thread and bring up both a disassembly and source view for the context.
3.) Set a breakpoint in the disassembly view.  Check the scope.  Note that the scope is set to the connected contexts.
4.) Set a breakpoint in the source view.  Check the scope.  Note that the scope is only for the context in which the BP was planted.

In the above test case, the expected behavior would have been to have all context which are executing code out of the same module, would also be scoped to the BP (or all contexts which are associated with the given memory context).

Comment 1 Eugene Tarassov

2012-01-12 14:17:09 EST

I cannot reproduce. When I try it, source breakpoint is planted in all
contexts which are executing code out of the same module - as expected. What target are you using?

Comment 2 Scott Tepavich

2012-01-13 01:05:44 EST

I tried this with a linux process, and the BP was planted in the context of the process (expected).

My previous target was a hypervisor target.  Something wrong must be occuring there.

Comment 3 Eugene Tarassov

2012-01-13 15:45:55 EST

As I understand, it is same for hypervisor: the breakpoint is planted in the hypervisor process (or address space) and single breakpoint instance handles all hypervisor threads.