Community
Participate
Working Groups
Mylar filter in Debug view is interfering with stepping. So, if filter is on and I step into a method (F5) under debugging, stack trace is not updated and as result editor for new method is not opened.
A related problem is that when a breakpoint is hit the stack trace will not show. What we need to address both these problems is a 'breakpoint interaction monitor'.
It seems like current implementation of the Debug view filtering can be improved in several ways: -- filter out all the threads except those in states "suspended" or "stepping" (take thread groups into the account and don't filter nodes for VM and processes) -- for suspended thread only filter stack trace from bottom up to the first class that is included into the current context. Make sure that above stack frames are NOT filtered.
That sounds right to me. Anything above the stack is implicitly interesting. It reamins to be seen whether this should be implemented with predicted interest (and affect other tools/views, e.g. active test suite), or whether we should have an implicit interest rule for this view only (easier, but often this approach turns out to be a hack).
Fixed, i.e. should not be interfering with stepping anymore, but may still want to show the newly interesting (stepped into) frames. And I added code for the debug structure bridge to be able to look up and down the stack as needed, so it should not longer be too hard to do.
