Bug 415130 - [debug] double clicking stack trace does not reveal the location
Summary: [debug] double clicking stack trace does not reveal the location
Status: CLOSED DUPLICATE of bug 414371
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.3   Edit
Hardware: PC Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2013-08-15 04:43 EDT by Jan Koehnlein CLA
Modified: 2013-08-15 12:31 EDT (History)
2 users (show)

See Also:

Attachments
Screenshot (161.67 KB, image/png)
2013-08-15 05:21 EDT, Jan Koehnlein CLA 		no flags Details
View All 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 Jan Koehnlein CLA 2013-08-15 04:43:13 EDT 
Steps to reproduce

- Debug a Java file such that it runs into a breakpoint 
- scroll the editor such that the stopping line is no longer visible
- double click on the stack trace element in the Debug view
-> nothing happens, the stopping line stays out of sight.

This is additionally problematic, when automatically switching to debug perspective: The editor is usually a bit smaller there resulting in the stopping line getting out of sight. In order to reveal it, I have to select another stack trace element first.
Comment 1 Dani Megert CLA 2013-08-15 04:56:50 EDT 
This works fine for me using 4.3 [1] or 4.4 M1 [2] on Windows 7. Can you try with one of those builds (no additional stuff)?

[1] http://download.eclipse.org/eclipse/downloads/drops4/R-4.3-201306052000/
[2] http://download.eclipse.org/eclipse/downloads/drops4/S-4.4M1-201308072000/
Comment 2 Jan Koehnlein CLA 2013-08-15 05:02:05 EDT 
I am using Eclipse Juno on a Mac.
Comment 3 Dani Megert CLA 2013-08-15 05:03:46 EDT 
.(In reply to comment #2)
> I am using Eclipse Juno on a Mac.

Closing then. Lots of fixes in that area have been made during Kepler.
Comment 4 Jan Koehnlein CLA 2013-08-15 05:04:25 EDT 
Sorry, it's Kepler.
Comment 5 Dani Megert CLA 2013-08-15 05:06:52 EDT 
(In reply to comment #4)
> Sorry, it's Kepler.

Are you sure? ;-).

Please try whether you can reproduce it using a clean install as indicated in comment 0.
Comment 6 Jan Koehnlein CLA 2013-08-15 05:21:30 EDT 
Created attachment 234449 [details]
Screenshot

Attached a screenshot made with a clean Eclipse Kepler Standard on MacOSX 10.7.5, Oracle JDK 1.7.0_25.

Is the entire JDT team working on Windows? I am asking because this one is 100% reproducible on my Mac, in Kepler as well as in Juno.
Comment 7 Michael Rennie CLA 2013-08-15 12:31:43 EDT 
(In reply to comment #6)
> Created attachment 234449 [details]
> Screenshot
> 
> Attached a screenshot made with a clean Eclipse Kepler Standard on MacOSX
> 10.7.5, Oracle JDK 1.7.0_25.
> 
> Is the entire JDT team working on Windows? I am asking because this one is
> 100% reproducible on my Mac, in Kepler as well as in Juno.

This is a dupe of bug 414371.

*** This bug has been marked as a duplicate of bug 414371 ***