Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsWhite Papers
Discussion GroupsFirst AidDatabasesJavaBeansGUIJava 3DVirtual MachineCORBASecurityToolsGeneral
Java DirectoryOpen Source ProjectsSample Book ChaptersUser GroupsWeb Resources
Related Topics
Databases.NETMore Topics ...

Java Forum / General / July 2006

Tip: Looking for answers? Try searching our database.

Eclipse Debug

Thread view: 
Barbara - 19 Jul 2006 15:03 GMT
Hello!
Someone can tell me how (if it's possible) to debug the method inside
the invoke call with eclipse.

For example, if I have this:

Method method = srvc.getClass().getMethod(service.method, null);
method.invoke(srvc, null);

when I debug the second line, I want to debug srvc and not only the
invoke method.

Thank's
Barbara
Oliver Wong - 19 Jul 2006 15:49 GMT
> Hello!
> Someone can tell me how (if it's possible) to debug the method inside
[quoted text clipped - 7 lines]
> when I debug the second line, I want to debug srvc and not only the
> invoke method.

   If you keep on pressing F5 (step into code), doesn't it eventually take
you to do underlying implementation method?

   - Oliver
Barbara - 19 Jul 2006 17:59 GMT
Oliver Wong ha scritto:

> > Hello!
> > Someone can tell me how (if it's possible) to debug the method inside
[quoted text clipped - 12 lines]
>
>     - Oliver

If I keep on pressing F5 it runs thru the invoke method but not thru
the method invoked by invoke.

Barbara
Roland de Ruiter - 19 Jul 2006 17:58 GMT
> Hello!
> Someone can tell me how (if it's possible) to debug the method inside
[quoted text clipped - 10 lines]
> Thank's
> Barbara

Did you enable "Step Filtering" in Window > Preferences > Java > Debug >
Step Filtering? Further, you'll need to enable the toggle button "Use
Step Filters" in the Debug View (it's the button to the left of the 3
Maximize/Minimize/Menu buttons).
Signature

Regards,

Roland

Chris Uppal - 20 Jul 2006 08:53 GMT
> when I debug the second line, I want to debug srvc and not only the
> invoke method.

I doubt if it can be done.  Since the JVM itself doesn't really "know" what
method it is going to invoke until it gets there, it would take some special
cleverness by the Eclipse people to work it out in advance.  I suspect you'll
just have to put breakpoints in the target method(s) yourself.

   -- chris


Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.