I just created a Amazon EC2 due to limited ram size on my workstation. Thus I need to figure out how to conduct remote debugging on this remote instance.
First of all, I am not quite sure I understand the difference between "Attach to Applicaton" or "Remote Application" in debugging configuration tab. From what I've learned, the first one is just using Eclipse as a front-end GUI to connect a remote gdbserver. But I have no idea what the second one means.
Right now I can connect to the gdbserver on my EC2. However, gdbserver gives me a warning message
Could not load vsyscall page because no executable was specified
try using the "file" command first.
I've already defined the executable as well as project in Eclipse's debugging page. Is there anything I missed?
I have done the same thing some time back and it was working absolutely fine and I have mentioned all the step in my blog. Check the link for detail description.
Related
I apologize if this is not the right place to ask such question, but I'm at my wit's end since Embarcadero's forum won't allow me to post any question there.
I have enabled the "Deploy" feature in the C++ Builder IDE, to test out about the depending dll & bpl files of my application, when I'm done, I found myself trapped in an annoying state - I can't perform any debugging without connected to a remote pc (with their PAServer)! This is causing a HUGE problem for me as I will not be able to debug my application if I'm away from the office, i.e. I'm on a field service at my client's place or at home.
I tried deleting the deployment profile, but it just get recreated every-time I compile my project and there is a DEPLOY command upon running compiling and running the source code. I have to wait until the connection attempt to the remote pc time-out to continue testing the application by manually clicking the .exe of my application.
Is there any way to turn off the "Deploy" feature so that I can do debugging on my local machine just as before activating the "Deploy" feature?
I've found out where the profile was hiding and deleted it, now I can debug as usual.
In the Rad Studio help:
ms-help://embarcadero.rs_xe5/rad/Connection_Profile_Manager.html
On occasion, I have this same problem with DelphiXE5 (where the problem is that I forget how to get back to the default environment without losing my remote settings.)
Remote Deploy active:
The Revert option for the normal build/debug environment:
And finally, the previous Remote Deploy settings available via the same Target Platform context menu (i.e., Properties):
The Default Connection isn't something to be setup. To the contrary, it's really not a connection at all. The Revert... menu item essentially means Revert to local build & debug.
I have made some code changes and deployed the code to Jetty Server which is located Remotely .
Accessed the application through browser and I am trying to debug a Application .
Please tell me whether i need to select the Local File Or Shared File from the Eclipse Debug Configurations .
Please see the screen shot here .
The option shown in your screenshot will not help you automatically get code deployed to your remote Jetty.
The option simply allows you to Share your launch configuration (Remote Java Application - ManageWatchlistCall) in your eclipse workspace. This will allow you to checkin the launch configuration in a versioning control system so your colleagues automatically get the sme Remote Java Application launch configuration.
in order to get new code to your remote server, there are only 2 options :
Redeploy your application on the remote server.
Hotdeploy pieces of code to the remote supported (if the server supports it)
Use Hotswap Bug Fixing (works for small fixes) (*)
(*) If you are running Java Virtual Machine (JVM) V1.4 or higher,
Eclipse supports a feature called Hotswap Bug Fixing (not available in
JVM V1.3 or lower). It allows the changing of source code during a
debugger session, which is better than exiting the application,
changing the code, recompiling, then starting another debugging
session. To use this function, simply change the code in the editor
and resume debugging.
Yesterday I installed OpenEdge Architect 10.2B (that is Object Oriented Progress adopted to Eclipse IDE) on my Windows 7 premium platform. The installation went fine without any error messages.
When I start OpenEdge Architect I get the following error message:
"Not licensed to run OpenEdge Architect for version 10.2B".
This error message is strange since it is not the case.
Also, it seems like parts of the Eclipse-plugin are blocked
The main menu looks ok
In the views there are error messages like: "Could not create the view: Plug-in com.openedge.pdt.text was unable to load class com.openedge.pdt.text.explorer.OEExplorer...."
I noted that if I open my firewall (F-Secure) and choose to allow all, then everything works fine but then, of course, the computer is vulnerable. Then I thought I should abandon the F-secure firewall and use Windows firewall instead, setting up exceptions for OE Architect. But at this point I can not see what the exceptions should be since there are plenty of processes involved!
Any suggestion on how to proceed? How can I see what is blocked (is it Eclipse related or Eclipse plug-in related or is it something else in the OpenEdge package?)
Migrated from https://softwareengineering.stackexchange.com/
I solved the issue, this is how I did it:
Open F-secure, change the firewall setting to allow all.
Open Windows firewall, turn it on.
Start OpenEdge Architect
A warning from Windows firewall appears a .\jre\bin/javaw.exe is blocked by the firewall, check the allow boxes and press "Allow access".
Done.
It my be that the license manager is a process itself thatthe Architect is only connecting to - thus the problem with the firewalls. Most of this stuff is either a java process or one of the processes from your \bin directory. To figure out which process is trying to open which port, open a command shell (windows+r, enter 'cmd' and press 'run'), and then run 'netstat -ao', which gives you a list of all processes running and the ports thy are listening on. If you search this list while running the Architect with your firewall turned off, you might be able to find the processes involved with licensing (either a java process or one of the binaries from the aforementioned 'bin' folder).
hope that helps!
I am trying to get the debugger (CF extension for Eclipse) working for last few hours. And struck in strange situation.
My settings are listed below
ColdFusion 8
Eclipse 3.4
I set up the RDS & modified the JVM.config settings and verified the connection & debugger, both returns successful in test run. But When i attach a debugger to the site, breakpoints are not hit.
My Eclipse workbench & site virtual directory pointing to the same path. It is in a remote server.
I left Eclipse-CF mapping blank since both pointing the same remote path.
And i am using WYSE thin client emulator.. does it anything to do with this..?
Can someone help me to resolve this problem?
Cheers
If your eclipse configuration is ok, could be that something is not confgured right on server side. Check if Line Debugger Settings > Allow Line Debugging feature is enabled and that Debugger Port (5005) is opened and accessible form client machine.
Articles that should walk you through proper setup:
http://eclipse.sys-con.com/node/382427
http://www.adobe.com/devnet/coldfusion/articles/debugger.html
Also you could try using CF Builder and/or FusionDebug http://www.fusion-debug.com/fd/ .
You do need to specify at least one mapping. Eclipse needs to know what folder in your project maps to the http root. Even if the mapping is / -> /, you need to specify that. The only time you can leave mapping blank is when the CF server is on the same machine as Eclipse.
Although I found PL/Java a powerful add-on for PostgreSQL, I couldn't find a way of remotely debug the clases loaded on the PSQL DBMS.
Is this possible to achieve?
Thanks in advance!
I suppose you could set pljava.vmoptions to enable debugging and include a port number to listen on, and then use Eclipse's "debug remote application" launcher to connect to it.
So a JVM option -agentlib:jdwp=transport=dt_socket,suspend=n,address=localhost:55000 will make the JVM listen on port 55000 for debuggers. You then open the "Debug configurations.." dialogue in Eclipse, right click "Remote Java Application" in the launch types pane on the left and update the connection properties on the right to use port 55000. You should connect up the debug launcher with a project as well, to pick up that project's class path and sources.
Note I haven't actually tried this in postgresql, but this corresponds to how I always used to run JBoss from a shell script rather than from within Eclipse.
I needed a slight change to the option line. The working one is-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=localhost:8000. Without the server=y part, the debugger complains about missing transport. With the above, everything worked.