My goal is to debug Haxe application in Eclipse (publishing SWF) on Linux. I have manually installed Eclipse Helios, Flash debugger version and Haxe. I have installed Eclihx. Problem is that I'm getting message from Eclipse:
Flash debug runner. This feature isn't ready!
Note: I can run program, so Haxe compiling works. I have also tried adding -D and -debug to hxml. I've been Googling out there, but no success.
And also, I don't know how to setup Eclipse so when I do run that automatically browser pops up with html.
From what I know, it's not currently possible to debug Haxe from Eclipse. However, you could compile a debug Haxe build and and use Adobe's fdb.exe, which is the command line debugger for Flash. With it, you should be able to set breakpoints and do some run-time state inspection. Hope this helps!
Related
I am using eclipse(Eclipse Java EE IDE for Web Developers.
Version: Oxygen.1 Release (4.7.1)). Currently I am experiencing problems debugging my project. When I run a junit in debug mode, it doesn't go into debug perspective and doesn't stop at breakpoints. The "skip break points" button in not pressed. Also when I try debugging another project I have no problems, but in this it just won't work. If you need any more info, I would gladly provide it.
I'm using Eclipse CDT on Windows 7, with MinGW as my toolchain and GDB as my debugger. For the most part I have been able to get everything working normally, including the development of Java, C/C++, and JNI applications.
However, I am unable to debug the native side of those JNI applications. The Java debugger works fine for Java code and GDB works fine for purely native code, but I cannot seem to get GDB to operate properly on code within a JNI .DLL.
I have searched the web for quite a while regarding this, and it sounds like the success people have had is by attaching to the running Java process after launching it from Eclipse. Then, setting a breakpoint and letting GDB hit it. Unfortunately, this does NOT seem to work for Windows users.
The only advice that seems to work ( which I can confirm ) is to launch the Java application in Eclipse, then attach to the process from Visual Studio. From there you can set breakpoints in the native code, and they will be hit. This approach is a pain in itself, but what really makes it awful is that you need to have compiled the .DLL from Visual Studio in order to generate the .PDB file for debugging symbols. Making the whole CDT somewhat extraneous at that point.
I'd much prefer to stay within Eclipse, but only if I can actually debug with it. Can anybody out there confirm if it's possible to debug JNI code with Eclipse CDT from Windows?
After a bunch more digging, I have confirmed this is definitely possible with the current ( Kepler ) build of Eclipse and MinGW.
That seemed to be my problem actually; the version of GDB I had wasn't able to attach to any process at all ( which I verified from the command line ). After updating to the current version of MinGW with a new gdb.exe, I could attach properly and view all the threads. Getting breakpoints to hit took a bit more work ( I was missing -g from the gcc compile ), but after that all seems fine.
I went through few queries on Eclipse CDT and GDB but I am getting more confused. I am a newbee to both GDB and eclipse.
My problem is as follows:
I have got test.exe file generated by Cygwin with a set of make files etc.
I can perform debugging using the command gdb ./Test.exe from the directory. This debugging is very sparse.
I learned that eclipse can interface with Gdb debugger and give nice GUI and debugging facility.
I will be grateful if someone can show how to load this test.exe in eclipse and run the code.
Thanks
Switch to c++ perspective in Eclipse.
Select Run -> Debug configurations in menu. Select C/C++ application and click on "new launch configuration" icon. Click on browse button to locate your executable, apply configuration and click the "Debug" button.
This should launch your application and locate sources, provided you compiled with -g3 (or similar). Make sure you also used -O0. (BTW: I tried this with mingw, not cygwin).
You could import Makefile project into Eclipse/CDT and use Eclipse for development.
I've been trying for a few hours now to make eclipse, mingw and Qt work, and I can't manage to.
No matter what I try, when I try to run the qt application (using Run or Debug, same thing), no window appears, and after a few seconds, Eclipse says 'program terminated'. Another time I tried (using some different configurations), windows would give that "Program has stopped" error.
If I try to launch the application from outside eclipse, I get a missing .dll error.
I have Qt 4.8.1 installed, latest version of eclipse, and I just installed the latest version of MinGW. I am also using the Qt plugin for Eclipse. I'm running Windows 7.
There are also some other minor problems:
For some reason I have to rebuild the index after opening/creating a project, or I'll get 'undefined include' errors.
The build (hammer) icon in the toolbar is grayed/disabled, why could that be?
For every new project, I need to change the make application to mingw32-make, is it possible to make the toolchain use this make executable or something?
I can't understand why Microsoft Visual Studio just works, I didn't have to set up anything other than install the Qt add-in, and Eclipse is so hard to configure...
I come from a background in C++, Python, and Django and I'm trying to expand my horizons and learn Scala and Lift. However, I'm having a really hard time figuring out how to debug Lift applications using eclipse.
I can create projects using some of the lift sbt templates and run them no problem. However, I haven't been able to start the application from within Eclipse because it can't find Jetty, and as a result, I'm not able to use the debugger to step through the Lift code. Weeks of googling haven't helped much.
Could someone share their methods or suggestions? I'm also new to the jvm, so feel free to share best practices or point out important differences that I may be missing.
Ok, I've gotten this figured out.
So I'm not actually launching the application from the Eclipse debugger. I'm starting the application through sbt, and then connecting the Eclipse remote debugger to the sbt vm that's running the webapp.
Here's what I did:
Assuming you have sbt-launch.jar in /bin:
Create the file /bin/sbt_debug with permission to execute and containing this line:
java -Xmx512M -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005 -jar /bin/sbt-launch.jar "$#"
What this script is doing is starting sbt and instructing the jvm to allow debugging on port 5005
Go to your lift project directory in your terminal and enter sbt_debug. Once you're in the sbt console enter container:start / container:update or ~jetty:start / ~jetty:update depending on which version of sbt you're using.
Next go to Eclipse, click the debug icon and select "Debug Configurations..."
On the left column, click "Remote Java Application" and create a new debug configuration. Set the Port to 5005.
Hit the Debug button and the Eclipse debugger should now be debugging the sbt process you started earlier
Note: This is the first method that has worked for me. If you have one that is better, please share
I've found the most useful tools to be the SBT Eclipse Plugin and the RunJettyRun plugin for Eclipse. The former will allow you to generate Eclipse config files based on your SBT setup and the latter will launch Jetty from Eclipse with the debugger attached. An added bonus is that generating your Eclipse config using "eclipse with-source=true" from the SBT prompt will download and attach src jars as well so you can step through Lift and any other 3rd party libraries you depend on as well as your own code.