Variables in Cobol with out dropping into C

[akbrant]

HI all,

This is awesome! I rebuilding a Cobol app that was last compiled in the 80's . Your tool has really been helpful but I've never been able to see the COBOL-VARABLES in the local debug window. My local variables look like b_12, b_13, b_163, etc.
I'm using the MS build of GnuCobol version 3.1

I've been a command like this to compile: cobc -xvg -static FILUPP.COB.

Thanks for the awesome, tools!

[OlegKunitsyn]

Thank you. If you really like the tool, simply star it here and on https://marketplace.visualstudio.com/items?itemName=OlegKunitsyn.gnucobol-debug#review-details to involve more maintainers.

Unfortunately, I can't support you on Windows. I just compiled GC 3.2-dev Docker image and successfully debugged COBOL programs in test/resources directory. Here is my launch.json:

{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "COBOL debugger",
            "type": "gdb",
            "request": "launch",
            "cobcargs": [
                "-free",
                "-x"
            ],
            "coverage": false,
            "verbose": false,
            "docker": "olegkunitsyn/gnucobol:3.2-dev"
        }
    ]
}

Please try and submit more details.

[akbrant]

OK! I would like to start a windows support group, as we know we need it! Star Star Do you think it possible to see the real cobol variables using windows and gnucobol built with windows tools?

[GitMensch]

It is possible and it does work if you use a MinGW built of GnuCOBOL. For this extension to work with a msvc built of GnuCOBOL we'd need support for lldb first (at least it is said to work also with pdb instead of DWARF, which is used by GDB).

[OlegKunitsyn]

OK! I would like to start a windows support group, as we know we need it! Star Star Do you think it possible to see the real cobol variables using windows and gnucobol built with windows tools?

Thank you! @mayhd3 is your friend there.

[GitMensch]

If you need to debug GnuCOBOL modules that were created by a MSVC-configured cobc you may want to have a look at GixIDE

[akbrant]

Okay thanks for taking a look. I would love to use MinGW based Gnucobol but I'm building a Windows 32 Cobol application (I have to use some win32 apis) The program also uses a c driver for the database. For some reason when I compile with Mingw based Gnucobol the database driver has runtime errors. When I use the msvs configure gnucobol build everything works fine. I'm away from my office for the weekend but I will take a look at your suggestions early in the week thanks again.

…

On Sun, May 23, 2021, 3:45 AM Simon Sobisch ***@***.***> wrote: If you need to debug GnuCOBOL modules that were created by a MSVC-configured cobc you may want to have a look at GixIDE <https://github.com/mridoni/gix> — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#106 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIPPXSBIICD35QRYX26LI3TPDTEDANCNFSM45KI3ACA> .

[GitMensch]

I would love to use MinGW based Gnucobol but I'm building a Windows 32 Cobol application (I have to use some win32
apis) The program also uses a c driver for the database. For some reason when I compile with Mingw based Gnucobol the database driver has runtime errors. When I use the msvs configure gnucobol build everything works fine.

Sounds like something that should be investigated as possible bug over at the GnuCOBOL discussion board. I Invite you to write about the issue there, ideally providing a minimal example, at least providing the full cobc command you've used and the output of it when you add -v (for both MSVC and MinGW). So far I assume you may need to add some link option and it would work identical on both sides.