We use to debug an application with cobanimsrv under ServerExpress 5. We start cobanimsrv and then start an application that calls a daemon to communicate with cobol. When cobanimsrv is started, it waits for our application to start. Once we have launched our app (via Adobe Air), we can debug the cobol code with anim.

Is there an equivalent of the cobanimsrv command for VC2.1 for Eclipse in order to debug a program from inside Eclipse ?

Thank you


  • Verified Answer

    Hi Alain,

    Yes, I can confirm that there is an equivalent of this functionality in the Visual COBOL for Eclipse product.  

    As a matter of fact, there's a lot more support for remote Unix compilation and debugging in the VC product.  You can now maintain, compile and debug your Unix/Linux applications with an Eclipse IDE running on Windows.  

    The debugger daemon and servers all run on the remote Unix machine in much the same way as they did with ServerExpress except that all the settings are handled for you rather than having to manually set port numbers etc.  The user experience is much smoother and less prone to error.

    You will want both a copy of the VC for Eclipse product and the VC Development Hub (the Unix parts).

    All manner of debugging scenarios are supported: waiting for application attachment, attaching to a running process, launching the process for debug and just in time debugging.  



  • Hi Darren,

    I am coming back a long time later!

    In fact, all is running on the same Linux server.

    With cobanimsrv, the scenario is easy : we open a console, we go to a specific directory, we start cobanimsrv, we start an application from a daemon calling a program situated in the mentioned directory and the debugger starts.

    How can I reproduce that with VC2.1 ? I haven't found a concrete example in the documentation.



  • Hi Alain,

    Yes, with Visual COBOL for Eclipse working remotely with your Linux server, you can reproduce the cross session debugging you had with cobanimsrv. These steps assume you have a Remote COBOL Project already created in Visual COBOL for Eclipse, and that you've used that project to build your executable:

    1. Within Eclipse, create a new Debug Configuration:
      1. Ensure your Remote COBOL project is open and highlighted in the COBOL Explorer view
      2. Right click on the project, and choose Debug As-> Debug Configurations (this will open a new window)
      3. In the list on the left, select "COBOL Wait for Application Attachment" as the type of Debug Configuration you'd like to create
      4. Click the "New Launch configuration" button above the list (looks like a sheet of paper with a plus on it) to create the Debug Configuration
      5. On the right, ensure the project name is filled in correctly
      6. Under the Matching Options, select the Radio Button labeled "Executables stored in directory", and enter or browse to the directory on the remote machine where your executable file resides
      7. If your application is 64 bit, be sure to check the box for that
    2. Click Debug to start the debugger waiting for new programs to launch in the directory you specified above
    3. At the command prompt on the LInux DevHub machine, make sure your environment in that session is set up for running COBOL. The easiest way to do this is to source a script we provide. If you've installed DevHub in the default directory, you can run the script with: "source /opt/microfocus/VisualCOBOL/bin/cobsetenv"
    4. Finally, cd to the directory containing your executable, and run it. You should see the debugger "catch" over in Eclipse, and be able to start debugging the program.

    If you run into any issues, please reply here, and I'm sure we can get you going.


  • Hi Again Alain,

    I wanted to let you know about a small correction I've made to the above post. You do not need to have an X Server running for this type of Debug Configuration - the user interface for your program will display in the Linux session where you've started the program, just as it did with cobanimsrv. Also, you don't need to enter anything in the "X Server (DISPLAY)" field on the Run Configuration dialog.

    Please let us know how it goes when you try out cross-session debugging in Visual COBOL for Eclipse.