Does anyone know why when I press the new button in Eclise Debug Configuration under C/C++ Application nothing happens?
Creating a new Java test configuration does work but I need to create a C/C++ Debug configration. I was able to with ease (on the same project) under linux.
This is under OS X.
I was able to get this working by creating a sample C/C++ project and adding the debug configuration there. The configuration is then available to the Java (Android Native) project.
Strange as the project already has the CDT nature added to it.
Related
In Eclipse IDE I can’t set the debug level and optimization level no matter what i do.
The problem is when i try to set the debug level and optimization options under Project Properties > C/C++ Build > Tool Settings > GCC C++ Compiler > Debugging/Optimization. After selecting any option in the pulldown box, it pops back to “None” in both boxes.
I tried to create a new workspace with a new project, i tried to erase the system workbench and install again , make new projects with different processors.
Why can’t I change these settings?
By the way in another PC everything is working.
my versions:
Eclipse IDE Version: Neon.3 Release (4.6.3)
System Workbench for STM32 - OpenOCD (for Windows 32bits)
Version: 1.16.0.201807130628
windows 10 64 bit
Thanks
Sergey
I am currently working on eclipse plug-in that involves many modules, and I would like to debug and run this eclipse plug-in from IntelliJ.I open this project in IntelliJ to edit code but when I have to run/debug this project I have to open eclipse IDE and start it from there. How can I use IntelliJ to do this?
I haven't actually tried this ... but you could try launching the RCP application stand alone but with the remote debug parameters specified for in your application's .ini file.
Then just point IntelliJ to the appropriate source and attach it's debugger to the running app.
Why do you want to do that? Eclipse has multiple tools for the plugin development that you will miss in IntelliJ. Also you need to build your plugin as product headless and then attach a debugger to it.
In my opinion it doesn't worth the effort. I would install Eclipse and devolop with eclipse.
Is there a way I can debug my application (using breakpoints in eclipse) while running it from command line (ubuntu)? I'm using Eclipse Kepler version on Ubuntu 12.04LTS.
I know there's something like attach to process in .net, was wondering if eclipse has some such setup.
Thanks,
Is your application written in C or in Java?
If your application is in C and you are using CDT, you can attach to existing project by:
Run your application from terminal.
In Eclipse CDT, go to main menu "Run"->"Debug Configurations...", double-click "C/C++ Attach to Application" and press "Debug" (you should not need to specify executable and/or project).
For Java applications, see this
This is my first attempt at creating an Eclipse plug-in. I've created one, along with a feature and update site. I set the target platform as my local Eclipse installation. When I run/debug the plugin from within the development environment everything works fine.
Now, my colleague installed the plug-in from the update site that I hosted. When he starts using any of the functionality exposed by my plugin he gets runtime exceptions.
He sees null pointer exceptions which didn't occur when I ran my plug-in project from my development environment.
I have a wizard that's part of my plug-in. When he close it he gets a "Unhandled event loop exception", and the wizard doesn't close. I didn't have this issue when I was running/debugging my plugin in my development environment.
Now I'm confused as to why the same plug-in is behaving differently in the production environment, as against the dev environment and when I was debugging it from my IDE. The target platform in both cases is the same Eclipse version. What could be the reasons?
And how do I debug the plug-in in a production environment? Is there a remote debugging capability for debugging the plug-ins on the production environment?
Any suggestions would be really useful!
To remote debug your plug-in, first add debug arguments to your target Eclipse .ini file
-vmargs
-Xdebug
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=1044
before launching it.
Then open another Eclipse instance with a workspace containing your plug-in project.
Open Run > Debug Configurations..., select Remote Java Application and create a new configuration.
As Project, browse and select your plug-in project.
Also fill in your connection properties (host of target Eclipse and port 1044).
Launching the newly created debug configuration allows you to debug your plug-in the same way you debug locally.
Now I'm confused as to why the same plug-in is behaving differently in
the production environment, as against the dev environment and when I
was debugging it from my IDE. The target platform in both cases is the
same eclipse version. What could be the reasons?
This is a classic: Eclipse plugins and RCP applications do indeed behave differently between PDT (the Eclipse IDE) and the exported product.
In your case, a NullPointerException thrown from the exported version but not from Eclipse is 9 times out of 10 an image or other resource files (properties, etc.) that is loaded by your code but is not listed in the build.properties of your plugin.
Anyway, you'll need to check the logs to retrieve the stacktrace and hunt down its cause. Such logs could be found in your friend's workspace under le .metadata/.log file
From your development workspace as it stands now, use the "Debug As -> Eclipse Application" menu item to startup a test workspace. When it starts up, you'll have two workspaces running: the original development workspace and the new test workspace. You can set breakpoints in your plugin code in the development workspace and run your plugin in the test workspace.
When your plugin execution in the test workspace gets to one of your breakpoints, execution will pause and you can use the Debug view in your development workspace to look at variables, set more breakpoints or anything else you want to do to debuf your plugin.
See the Apache Wiki for Developing with Eclipse.
Under Windows 10 with Tomcat running as a windows service I started:
tomcat8.5\bin\Tomcat8w.exe
& added in the Java tab as the first entry in Java Options to enable remote debugging:
-agentlib:jdwp=transport=dt_socket,address=8000,server=y,suspend=n
I need some help with trying to setup C++/Java build using Eclipse. I am following this tutorial (http://www.raywenderlich.com/11283/cocos2d-x-for-ios-and-android-getting-started) but just can't understand why I keep getting "please define NDK_ROOT".
I updated the create-android-project.sh file and applied this cmd in Terminal: export NDK_ROOT="same path to NDK as in create-android-project.sh file". When I ran the 'create-android-project.sh', I had no problem with creating the project, Running the newly created project's build_native.sh also ran with any issues.
So after following the steps to update 'Build Command' from default to whatever the tutorial is asking should compile the C++ and Java files in the project, without having to run the build_native.sh in terminal and the project in Eclipse.
If I remove the custom build to default all compiles and runs on the project on both the emulator and device.
I've attached a screenshot of the settings and Console log of the project build.
Dev Environment:
Mac OS 10.8 (Lion)
Eclipse Juno 64-BIT
Cocos2d-x v2.0-x-2.0.3
NDK: android-ndk-r7-crystax-5.beta2
Please advise.
I solved the issue by adding the NDK_ROOT variable to ADT > Preferences > C/C++ > Build > Build Variables.
Hope it helps someone, I know I've been looking for a solution for quite some time.
This error is not related to eclipse. It tell that the NDK_ROOT is not define in build_native.sh file. I solve the issue by adding NDK_ROOT at the top of the build_native.sh file
build_native.sh
NDK_ROOT="path of your ndk "
Actually you noly need to set it in C/C++ build-> Environment.
Just like this. It works for me eventually.
Refer to this picture for configuration
In the Left side pane of your eclipse , As I can read that Resources,Android ..etc
In that go in Android, there will be one option to set NDK path
Eclipse -> Window -> Preferences -> Android -> NDK -> set path to the NDK
It is same as you do it for android SDK , here you have to specify NDK path ...
EDITED:
If you still face the problem ...then it is the same problem which I faced while setting it up for my windows version
there is an issue with android ndk version for export NDK_Path .... You may try with crystax ndk version for android it will work for sure
Any more help please feel free to ask