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

Bug 439690

Summary:	Variable selection cleared when hitting break point repeatedly
Product:	[Eclipse Project] JDT	Reporter:	Martijn Dashorst <martijn.dashorst>
Component:	Debug	Assignee:	JDT-Debug-Inbox <jdt-debug-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	ed, sarika.sinha
Version:	4.4
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X
Whiteboard:	stalebug

Description Martijn Dashorst

2014-07-16 05:43:38 EDT

I have a breakpoint in a function that is repeatedly hit in a debug session. I select "this" variable in the variables view. I press F8/Run to let the program continue with processing the request, waiting for the next time the breakpoint is hit.

Expected behaviour:
 - the break point is hit
 - the variables display still has "this" selected
 - the variables display updates the content view with the actual value of this

Actual behaviour:
 - the break point is hit
 - the variables display has forgotten the selection of "this"
 - the variables display's content view is empty
 - cramp in my arm for having to move the mouse pointer from the Run triangle to the "this" variable and clicking it

This bug behaviour is similar to #5188, #8941 and more recently #119025. But those were all reported to versions prior to E4.

Comment 1 Sarika Sinha

2014-07-16 06:56:47 EDT

*** Bug 439694 has been marked as a duplicate of this bug. ***

Comment 2 Ed Willink

2014-07-16 07:09:54 EDT

(In reply to Sarika Sinha from comment #1)
> *** Bug 439694 has been marked as a duplicate of this bug. ***

The reported behavior is inrtermittent ~50% of the time and has been a consistent feature of JDT for many years.

Comment 3 Eclipse Genie

2019-03-25 01:30:14 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 4 Ed Willink

2019-03-25 01:52:05 EDT

(In reply to Ed Willink from comment #2)
> The reported behavior is intermittent ~50% of the time and has been a
> consistent feature of JDT for many years.

I still see this, but clearly JDT users do not.

In Bug 528724, a similar 'JDT Debug' problem turned out to be a bug in a contribution by the ATL debugger.

It would therefore seem likely that this problem is caused by one of the following that I regularly use.

ATL, QVTo, Xtend

Possibly OCL, QVTd too, but I think this problem started before they acquired debugging abilities.

Comment 5 Sarika Sinha

2019-03-25 02:24:58 EDT

(In reply to Ed Willink from comment #4)
> 
> ATL, QVTo, Xtend
> 
> Possibly OCL, QVTd too, but I think this problem started before they
> acquired debugging abilities.

It be better to move this bug to one of these component?

Comment 6 Ed Willink

2019-03-25 04:01:35 EDT

Maybe but which? I'll try to keep an eye out for a repro, now reminded that it might be not-JDT.

But it might be JDT/platform:

Intermittency: Perhaps the order in which alternate debuggers see the selection is unstable.

Failure: Perhaps there is inadequate tolerance of an alternative debugger rejecting a selection.

Comment 7 Ed Willink

2019-05-28 14:48:57 EDT

A solid repro for further investigation.

Debugging

  /org.eclipse.qvtd.build/.launches/Generate QVTd AS Models.launch

with a breakpoint at 

  org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl line 298

 (first line of doSave(OutputStream outputStream, Map<?, ?> options)

the VariablesView shows three variables:

this, outputStream, options.

With "options" selected to display its Map as a string value, every encounter of the breakpoint fails to show the String. Have to keep reselecting options.

?? Is it because both outputStream and options are 'yellow' ??