-
Notifications
You must be signed in to change notification settings - Fork 217
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debugger does not support decompilation #11
Comments
More information is also available at http://help.eclipse.org/mars/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Fguide%2Fdebug_launch_sourcelocators.htm |
Is there a fast solution for this? |
any thing happened with this.. I cant load decompiled code from the debugger |
Hi All, While working on any version of eclipse, add the required jars directly to your build path, not through any libraries....for me I have tried this on Eclipse Galileo as well as Eclipse Neon. I have deployed my application in tomcat, and added all the jars from WEB-INF/lib and .properties files from WEB-INF/classes directly to build path and removed the existing Web App library that takes the contents of lib/classes to the build path. If you work like this you will be able to debug inside jar files. Inside Jar files, you will not be able to check values of any local method variable or evaluate any expression manually, but you will be able to check any global variable (both class as well as member) value as well as arguments passed to the current method. |
have same trouble, too. |
jd-eclipse is never used during debugging. If you set a breakpoint in some decompiled code, Eclipse will stop there but will not show the decompiled source.
This issue was already reported in mchr3k/jdeclipse-realign#16.
Probably it can be fixed by implementing the extension point sourceLocators (http://help.eclipse.org/mars/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Freference%2Fextension-points%2Forg_eclipse_debug_core_sourceLocators.html).
An example can be found in https://github.com/eclipse/m2e-core/blob/master/org.eclipse.m2e.launching/plugin.xml#L200
The text was updated successfully, but these errors were encountered: