I use eclipse LUNA in that when I start debug mode the eclipse IDE will be closed. if any one can tell me why it happens and give the suggestion to solve it. And also tell me to start the template proposal because it won't start while entering ctrl+space,
you can probably raise a issue in Eclipse forum. If you dont have any specific requirements, you can probably go with Kepler as its more stable now.
Related
I am developer who is using xTend. The docs for this kind of programming language are introduced at this link:
https://www.eclipse.org/xtend/documentation/
When I used Eclipse Photon version to develop my product. I ran into the issue related to debugging.
AFAIK, xTend code will always be intermediately compiled to java code first.
The issue description as below:
The debugger can hit breakpoints if they are toggled in java code.
But, when I toggle breakpoints in xTend code, the debugger doesn't hit the breakpoints any longer.
I tried some times to refresh my Eclipse workspace (delete old one / create new one), even used other version of Eclipse. But, still didn't solve the issue.
Who had already run into this situation, could you share your idea or solution on this ?
I have resolved the problem.
This happened because the configuration not adequate.
If you have same situation to me,
please consider to check all below Eclipse debugger's configurations.
Everything was working just fine, but then when I tried to debug again my app. It didn't work and instead, I got the message,
"alternative source available for the class java.lang.class android studio"
I didn't know what it meant. I clicked on disable, now I can't debug anymore and it says the library Dalvik.annotation.optimization.FastNative is not found (java.lang.NoClassDefFoundError: Class not found using the boot class loader; no stack trace available)
Does somebody know how to fix this issue? I can run the app, but as you know.. debugging is very useful, especially for someone like me. That has been working with android for just one month ago
I'm using Android Studio 3.6
This is the screen I get when I try to debug
Issues of that sort usually get fixed when you make a clean build then try again, if not try invalidating caches and restarting (File > Invalidate caches/restart)
At the end, the solution was to disable the breakpoints. Especifically the Java Exception breakpoints and Excepction breakpoints, also deleted all my breakpoints just in case. And I can debug again!
To delete breakpoints just go to Run>>View Breakpointsand and uncheck
I hope this helps other newbies like me
I've recently had my app moved from Websphere Application Server 6.1 to WAS 7.5, due to end-of-life for 6.1. Consequently, I needed to update my debugging server. I found this to be an opportune time to move my application from an IBM RAD IDE to Eclipse (already had Indigo installed). Or so I thought.
Anyway, the powers that be, here, have recommended taking my debugger all the way to WAS 8.5, since I'm only using it to debug.
But the issue that I'm encountering is that I cannot get the debugger to stop on my breakpoints. I've got approx. 10 breakpoints in my opening page, all in JSP/Java code.
I'm running Java 1.6.0_32 and Java SE Runtime Environment build 1.6.0_32-b05. I really don't know how to check which JDK I've got loaded. I've seen recommendations to "go back" to JDK 1.5, but I can't be certain that's not what I'm running.
And to cover a few other bases, I have JUST started my system for the day, opened the IDE, started the server in debug (says "Debugging, Synchronized"), put focus on the opening page of the application and clicked "Debug on server". The front page opens without stopping at any of the breakpoints.
Does anyone have ideas or suggestions?
If you use eclipse's debugger and running the application outside eclipse environment , we have to configure it as remote java application.
Also check if the code deployed in server is in sync with the one present in workspace.
anything wrong of the ecplise's site.
Run->Skip all breakpoints
Well, I had recently faced this problem, where the code did not use to stop at breakpoints while I was in debugging mode and was sure that the particular piece of code is executing. In order to solve the problem, I did a clean-build-republish but it did not work, recreated the profile and readded the server with new profile, still did not work then finally re-installed RAD and web-sphere but It still did not work. Then I found the below article
https://www-304.ibm.com/support/docview.wss?uid=swg21240896
and realized it could be a problem due to some other OS process interfering with debug process/port so I performed a system restore. After restore when I deployed the application, debugger started working properly.
I'd like to say I found the answer to this, but I never did. I ended up dropping RAD and moving to debugging on Jetty. My local testing isn't EXACTLY as it would be on the test server, but it works. Not sure if this should be flagged as "answered" or not.
UPDATE: I have left this project but before I did, the entire development platform was moved to IDEA and debugging was no longer an issue. I don't know if I should find a way to mark this question as inactive or closed or whatever so that it's not just sitting out here getting views and responses when it's no longer an issue for me.
This is Anas here and I just wonder if one can share his though about windowsbuilder on eclipse. I installed it from help link through selecting SWT, GWT other plugins and all gone well but after a restart those plugins are not working. Precisely, Eclipse IDE is showing those links enabled but it takes me to interface asking to install some additional toolkits, again when I proceed, I met a repository not found error.
Hunting over web, I have tried -clean and checked my port address. Thanks for your comment!!
Well Anas,
I understood your problem so follow these simple steps to overcome this solutions
First install the Indigo[3.7.2] version Eclipse from this link:
http://download.eclipse.org/releases/indigo
And then go to eclipse--->Help---->InstallNewSoftware and paste the below link>
WindowBuilder[1.6] Pro Update Site - http://dl.google.com/eclipse/inst/d2wbpro/latest/3.7
And select WindowBuilder Specific Checkboxes and proceed accordingly.
After that if you want to do a simple example of using windowBuider
just go through this link it might be helpful for you in this regard:
http://help.eclipse.org/indigo/topic/org.eclipse.wb.doc.user/html/NewComponentsTutorial.pdf
In case still you are facing issues feel free to reach me SUNIL
Check over here for available WindowsBuilder versions:
https://www.eclipse.org/windowbuilder/download.php
Take a link, and pass it on Eclipse IDE's feature installer, which takes the URI. Aim for the version of the builder which is supported by that IDE version.
If you take the latest version of WindowsBuilder, it does not mean that the specific IDE does support it.
Best regards
What’s the equivalent of
System.Diagnostics.Debugger.Break();
in the Java world?
Purpose: I have a tomcat based webapp launched by a custom build tool and need to debug the application in eclipse. In the .net world the above statement when encountered will prompt the OS to attach a debugger and I can attach Visual Studio to debug. I am trying to achieve the equivalent in java with eclipse
Here's an excellent article on remote debugging using Eclipse. They even have a section discussing Tomcat.
Here's a link that I used to debug web apps on Tomcat. It goes through installing Eclipse, Tomcat and Java and then setting up Tomcat to run in Eclipse. Towards the bottom explains how to debug a servlet in Eclipse.
http://www.windofkeltia.com/j2ee/wtp-tutorial.html
In general the Java program cannot tell if the JVM runs in debug mode or not, and there is no way to from your program to say that you always want to start a debugger HERE.
You can, however, tell the DEBUGGER that you want to have a breakpoint at a given location, and you will then enter the debugger when the program reaches that spot.
EDIT: You will need to investigate your launcher to see how you can trick it to contain the options needed to enable debugging in the JVM. You may also see if jvisualvm can give you the information you need as it can attach to an unprepared Sun JVM.