Simon Sobisch

> Or would you say even this compilation to C is an issue? Yes, I'd say. The compile to C looks for all sources specified, then reads all copybooks and...

Concerning the COBOL and C sources: of course they must exist for this extension to work as expected but it's possible in any way it should be done when necessary,...

In general: yes that was the idea. This should solve some issues we see for debugging complete COBOL applications and for attaching to a running process. I don't know how...

@brunopacheco1 Just a friendly ping: any update yet and/or the option to work on this soon?

As I just did another test of this on Win32 (now working) - the auto-recompile on each debug is really bad. I highly suggest (again) that this extension should _never_...

@ddeclerck @nberth could you tackle this? The combination of compiling and debugging (which kind of breaks "normal" programmer flow) is the one big issue this extension and therefore your fork...

How does your configuration look like?

> Is it possible that npm (nodejs) must be installed? No. > When I press F5 and select "Cobol debugger", als nothing happens. You _may_ have to create a launch.json,...

Follow-up to the 3rd point from above: Just tried to use this extension on a machine where the cobc executable was moved to another place - debugger starts (should error...

I hop that @OlegKunitsyn may merge this soon. In any case and "mostly unrelated" (at least unrelated to this repo, other than your changes being likely similar): @marcsosduma Can I...