Step Into problems with system classes

When stepping with F7 into a system class, IDEA stops at the first
line of code of a non-system class. From my point of view, this is
completely weird. I would expect IDEA only to stop at any position in
the call-stack.

Tom

8 comments

See Project Properties | Debugger | Do not step into the classes.

--
Valentin Kipiatkov
JetBrains, Inc
http://www.intellij.com
"Develop with pleasure!"


"Thomas Singer" <fake@fake.com> wrote in message
news:qo9qavk7knfdj8a66mf110r9evp6nuoeso@4ax.com...

When stepping with F7 into a system class, IDEA stops at the first
line of code of a non-system class. From my point of view, this is
completely weird. I would expect IDEA only to stop at any position in
the call-stack.

>

Tom



0

Valentin,

My point was not, whether such a step-filter is possible. I wanted to
express, that it should only stop at a source code on the existing
call stack, not anywhere deep in the method call.

Tom

0

I'm not quite sure what you expect from IDEA. But from my point of view the current behaviour is exactly what I expect and what is useful to me.

0

To speak about the same topic, here a small scenario

com.company.ourproduct.ClassA calls java.apackage.Something, that
calls com.company.ourproduct.ClassB (e.g. a listener).

When stepping through code of ClassA, I do not want to end up in
ClassB when stepping in Something, because there is a problem to come
back to ClassA (the usecases are much more complicated with, e.g.
Swing).

There is an alternative to my previous suggestion:

When stepping through code of ClassB, that was called by apackage,
there must be an easy way (beside breakpoints!) to step out or over to
ClassA.

Tom

0

I agree that the style of debugging where you set a series of break points in listener classes is somewhat akward.

Do you have an alternative suggestion? Maybe something like "Break upon entry into class?"

Mike

0

When stepping through code of ClassB, that was called by apackage,
there must be an easy way (beside breakpoints!) to step out or over to
ClassA.


Why don't you just use "StepOut" (Shift+F8) several times (till you get back
to ClassA)?
I agree this is a little bit annoying, but does not really cause a serious
use problem. Or does it?

--Oleg


0

>Why don't you just use "StepOut" (Shift+F8) several times (till you get back
>to ClassA)?

Try to do this if the call stack has 50 entries.

Tom

0


>

Try to do this if the call stack has 50 entries.


Yes, I agree. When I said it was a little annoying I meant just that...
I think you should file a feature request (or a bug?) to make the "skip classes"
behavior symmetrical, i.e. if your StepIn ends up in your own code
burried 50 levels deep in someonelse's crap then StepOut button should
bring you back where you belong (i.e. seamlessly perform 50 StepOut[s]).
The current StepOut behavior is inconsistent in that respect anyway.
I would vote for such a fix.

--Oleg




0

Please sign in to leave a comment.