Bugging into library files with selena

Is it possible to debug into library files with Selena? I have debug info compiled into the jars however I can't seem to step into library files. Should this be possible or am I trying to do something that's not supported?

3 comments

This should be possible, but probably your settings are configured in a way that you need to step in forcefully in the classes of that library (see "Force Step Into" action CtrlAltF7).

these settings can be found at the bottom of the general tab of the debugger settings. which can be reached by: Settings (CtrlAltS) | Debugger (G) | General tab | "Do not step into ..." at the bottom part of the dialog.

0

This should be possible, but probably your settings
are configured in a way that you need to step in
forcefully in the classes of that library (see "Force
Step Into" action CtrlAltF7).

these settings can be found at the bottom of the
general tab of the debugger settings. which can be
reached by: Settings (CtrlAltS) | Debugger (G) |
General tab | "Do not step into ..." at the bottom
part of the dialog.


Sadly that does not seem to do the job. I turned off Do not step into completely. I get as far as the method definition however it refuses to actually step through the body.

I suspect it may have something to do with my project setup.

I'll keep digging and see if I can find the root cause.

0

Okay. I feel very foolish now. I found the problem and it was that debug info was NOT compiled into the jar as I had thought. Idea 1, me 0.

0

Please sign in to leave a comment.