Bug 281278 - support jumping to debug thread stacktrace from breakpoint marker in source file
Summary: support jumping to debug thread stacktrace from breakpoint marker in source file
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.4.2   Edit
Hardware: PC Windows Vista
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-23 16:27 EDT by Ralf Hauser CLA
Modified: 2009-06-23 16:40 EDT (History)
2 users (show)

See Also:


Attachments
BreakPoint.png cite the Thread-name in the yellow pop-up (33.08 KB, image/png)
2009-06-23 16:27 EDT, Ralf Hauser CLA
no flags Details
BreakPointThread.png (35.90 KB, image/png)
2009-06-23 16:33 EDT, Ralf Hauser CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ralf Hauser CLA 2009-06-23 16:27:46 EDT
Created attachment 139912 [details]
BreakPoint.png cite the Thread-name in the yellow pop-up

Build ID: V3.4.2 M20090211-1700

I am debugging a tomcat with 2*25 listeners, so when hitting breakpoint, possibly multiple threads are stopped in various breakpoints and the currently focused marker in the source window not necessarily corresponds to the stack-trace visible in the debug window. Sometimes the stack-trace is also collapsed.

This makes it often quite hard to find which thread is stopped
Comment 1 Ralf Hauser CLA 2009-06-23 16:33:09 EDT
Created attachment 139914 [details]
BreakPointThread.png

on top of naming the thread that currently hangs in the breakpoint in the yellow pop-up, 
allowing to jump to there in the debug view by means of additional entries per thread suspended in the break-point at hand would even be nicer
Comment 2 Darin Wright CLA 2009-06-23 16:36:21 EDT
Many of the collapsing thread issues have been fixed in 3.5. See bug 212798. Please see if problems persist in 3.5.