Hi Dave, This is what I do:
Step 1: export JVM_DEBUG_PORT=<port you would like to use> Step 2: Start sqlci, it will print a message indicating that it's listening on a port. Step 3: In Eclipse, go to Run -> Debug Configurations and create a "Remote Java Application" configuration, entering "localhost" and the port you chose for debugging. Now you should be able to debug sqlci. It will enter the debugging state once sqlci hits some Java code. If you want to browse classes (both Java and C++) with Eclipse, do the following in the top-level directory (incubator-trafodion): make eclipse then follow the instructions printed at the end of this step. For debugging Java UDFs, see https://cwiki.apache.org/confluence/display/TRAFODION/Tutorial%3A+The+object-oriented+UDF+interface#Tutorial:Theobject-orientedUDFinterface-DebuggingUDFcode . I have not yet debugged mxosrvrs or ESPs, that probably adds a lot more complications. Hans On Thu, Apr 21, 2016 at 1:36 PM, Dave Birdsall <[email protected]> wrote: > Hi, > > > > There used to be a page on the older Trafodion web site that had > instructions on how to debug a Trafodion process (such as an ESP or > tdm_arkcmp) using Eclipse. That is, the process though largely C++, has > Java code in it, and I want to debug that Java code. As you can tell, it’s > been several months since I’ve done this so I’ve forgotten how. > > > > I remember there were some set-up steps (mvn eclipse perhaps?). I don’t > remember if there is a specific TCP/IP port that Trafodion processes use > for Java debugging (and I imagine that port would differ for different > instances on a development workstation). > > > > Can someone remind me how to do this? Your reward will be that I’ll restore > these instructions to our wiki. > > > > Thanks, > > > > Dave >
