Community
Participate
Working Groups
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
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
Many of the collapsing thread issues have been fixed in 3.5. See bug 212798. Please see if problems persist in 3.5.