marcsosduma / cobgdb Goto Github PK

if you type the S command twice too quickly the debugger freezes and remains frozen.

see attached screen.

When you type the Q (Quit) command the debugger send a message where is COBGBD instead of COBGDB.
See image:

Depends on #1.

Once this is implemented it would be easy to allow cobgdb 21321 (attach to pid) or cobgdb server:port (attach to gdbserver using extended-remote).

We already have "run to selected line" (C), which is often useful.

Especially if you recognized that there was an issue with a condition and want to jump into (or out of) its statenents, or when you want to do a missed CALL again (for example because you've used "N"ext instead of "S"tep an additional "J"ump to is very useful.

I managed to start a debug session.
the command I used is the following
cobgdb customer.cob -x -Tlista.txt
The system compiles the program and immediately starts the debugging session. See first attached screenshot.
Unfortunately the Step command doesn't work (it does nothing).
Only the V command which displays a list of some variables works (partially).

Starting from the second execution of the command:
cobgdb customer.cob -x -Tlista.txt
I get the error of the second screenshot.
At this point I can no longer run the debugger.

If data is invalid, then this may automatically be used (like x'202A20' in a COMP-3 field), but in any case it would be nice to be able to view (and after #5 is available also edit) in hex.

Ideally it would be able to set a condition to a breakpoint after it is reached (you set it at the start, then find that you only want to stop if a variable is > 42).

That would for example allow a gdb "knowable" user to do something like break faraway.cob:1335 or to skip WORKINGPROG

Hi,
just to ask if it is possible for the .exe executable or the executables for windows to be added to this site.
I would like to start using and testing the debugger but avoiding all the work of installing the various components necessary before being able to compile the source code.

The easiest implementation just works for simple PIC 9 / PIC X, and/or has no validation of the data. A more complex one could do the validation and adjusting as needed (the "upstream" extension should have code in for that).

The E command would be also useful to be handled within the current Variable displays (just popping up as another window).

if you find the need to do some pre-processing directly then have a cobcgdb wrapper (that would do cobc -g with every switch you find necessary - but a user may execute the same commands manually) and a cobgdb which is only the frontend

This has the benefit of allowing a connection to a running process/server later - and most important: people can compile now and debug 6 days later (or a real world application consisting of 500+ COBOL modules) without any problem. This is the biggest regression in gnucobol-debug which effectively prevents its use for those type of applications. Please don't copy that regression here.

As noted: really low-priority, but a nice to have:

• hover over variable with the mouse -> show its value after (a possibly configurable) timeout, maybe 1.5 seconds
• support for right click:
  • set/delete breakpoint at selected line (like B)
  • run to selected line (like current C)
  • jump to line (feature missing in general #8)