How do I fix a broken debugger, one that just won't start, in EclipseME (now Mobile Tools Java)?
(This question has an answer which will be transferred from another question soon)
The most annoying issue with EclipseME for me was the "broken" debugger, which just wouldn't start. This is covered in docs, but it took me about an hour to find this tip when I first installed EclipseME, and another hour when I returned to JavaME development a year later, so I decided to share this piece of knowledge here, too.
If the debugger won't start,
open "Java > Debug" section in Eclipse "Preferences" menu, and uncheck "Suspend execution on uncaught exceptions" and "Suspend execution on compilation errors" and
increase the "Debugger timeout" near the bottom of the dialog to at least 15000 ms (so the docs say; in fact, a binary search on this value could find optimal delay for your case).
After that, Eclipse should be able to connect to KVM and run a midlet with a debugger attached.
most debuggers are just plug-ins that also have a command-line interface; try running the debugger from the command-line and see if it works. If it does, then check the plug-in configuration; you may have to re-install the plug-in.
caveat: I have not used EclipseME, but had similar problems with the Gnu C debugger in Eclipse for Ubuntu.
Related
When running a file despite having a compiler error, I accidently marked the checkbox "Always run without asking". I regret this and would like NetBeans to ask me again before running a Java file that has compiler errors.
How can I do this? This should be simple but I cannot find any way...
As I can see from NetBeans bugzilla, this defect was left without reply: https://netbeans.org/bugzilla/show_bug.cgi?id=186776. For example, on my Windows 10 operating system I can manipulate this property using the C:\Users\<userName>\AppData\Roaming\NetBeans\8.0.1\config\Preferences\org\netbeans\modules\java\source\BuildArtifactMapperImpl.properties file, having now in it askBeforeRunWithErrors=true.
I'm new to Macs but I don't think this is a problem that comes from that. I've been attempting to set up GDB as a debugger for programming in golang on Eclipse. I know how to do it for the most part, but at some point one of the steps is to open up your debug preferences in the C/C++ configuration and fill in the path of where the debugger is located. Unfortunately, the option doesn't even show up for me:
Why doesn't the "GDB" option show up under Preferences >> C/C++ >> Debug? If i'm not mistaken, it should be a part of the CDT package correct? Am I just using the wrong version? It should be giving me this option:
At least it does for Neil Craft, the author of this tutorial
For anyone coming here looking for an answer:
https://www.ics.uci.edu/~pattis/common/handouts/macmingweclipse/allexperimental/mac-gdb-install.html#eclipse
If there is no GDB section in the C/C++Debug subtree, close the preferences window, and try to first start a debugging session for any project that you can already run without problems. You can do it by either clicking the Debug button on the toolbar, or selecting RunDebug from the main menu. This attempt will, of course, fail with an error message about the gdb command, but it will force the said C/C++DebugGDB settings to appear in the preferences.
I have a strange problem when using Pydev on my work machine (others at work have the same issue). It does not occur when I do this at home, which makes me think it's something to do with the environment at work. We are running Windows 7.
I am using Pydev 3.9.2 but the same thing happens with earlier versions. It occurs with all versions of Eclipse after 3.7. The problem is this. When I create a jython console (the one running in the Eclipse VM), the error output doesn't work. If I type an invalid python command, there is no output on the console. It just appears that the command worked. If I type a command such as "print 100", the output prints as you would expect.
The second problem is that if I hit the red square which is supposed to remove the console window, Eclipse crashes. There are no errors or any indication of what is going wrong.
I have tried different versons of eclipse, different versions of Pydev, different machines and it doesnt make any difference.
Has anyone seen this? I've tried everything I can think of to debug this issue so any help is appreciated.
thanks,
brian
Unfortunately those quirks are expected...
The internal console in Eclipse is mostly a developers SDK for experimenting with Eclipse itself and is not meant as a general shell (you should configure an interpreter and use it for that).
I don't have plans on improving on that situation (there's already a multi-year backlog on PyDev and this isn't really critical), but if you'd be willing to spend some time and fix those issues, pull requests would be definitely welcome -- see: http://pydev.org/manual.html for details on getting the code and setting up the environment.
When I open a pydev console, it takes several seconds before I get a cursor. I have a single file "Hello World" sort of project. There are no large variables to show.
My installation used Kepler-CDT, and I then installed PyDev (Latest, version 3.6.0)
I right select the console icon, select New PyDev Console, and then the console selection dialog appears. I select "Python console" (OK).
"Create Interactive Console" shows in the eclipse progress bar. Eventually, IPython starts, and after 20 seconds or so, I get a >>> prompt.
If I press enter at the prompt, another prompt appears as expected, but it usually take 4 or 5 seconds.
Some suggestions I have seen talk about firewall issues, how would I go about checking this?
How do I debug this problem?
What's your OS? From what you're saying, the issue really 'appears' to be either some network misconfiguration or possibly some firewall/antivirus making things slower (you can try disabling those to test if things go faster). As for a network misconfiguration, you can try checking your hosts file to see if things are correct there (I've had reports where there were other things, but these are the most common -- for other situations it may be more difficult to diagnose as usually each particular case is something different).
I could not debug using goclipse plugin, it was asking about gdb debugger then I downloaded the binary ver. 7.6 but now it is giving me "Source Not found"..
As suggest from many posts, I tried to build the program before going to start debugging but still it is giving me the same thing.
below is a secreenshot
even I found some guys were saying is to specify the working directory in configuration as "other" but still giving me the same error
finally, I fixed the issue by using the "gdb" distributed within liteide package. you could reference it from "Window | Preferences"