I could not get b.cbl to compile. It had errors, so I made some changes. See BB.COB attached.
Also the call to hexDump had problem, so I included MY version called HEXDUMP to the bb.cob program.
It now produces;
61313233343541
nb = +00007
0x00dd8090
9080DD00
Program runs on 32-bit architecture.
Character set is ASCII.
Byte order is little endian
Dump of memory beginning at address: 0x00dd8090
Length of memory dump is: 7
Sorry about that; i've sent the wrong source. My question was about the fact that ** cobgdb** does not seems to support user defined intrinsic functions and nested subprograms; they seems to be skipped. Am i wrong?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The main question for me is: Does it work with cobc alone? In this case: yes, it does.
So it is most reasonable to not post here but in the place where people discuss the development of cobgdb, that is https://github.com/marcsosduma/cobgdb/issues . As that software doesn't came out of nothing it would be interesting to know if issues you see with it are already part of its origin (in which both should be fixed) https://github.com/OlegKunitsyn/gnucobol-debug or are cobgdb-only (which also changes the way the developer would search for it).
In any case: be sure to post cobc --version as this makes a huge difference how the code is generated by cobc (which is "kind of reversed" with those extensions).
Last edit: Mickey White 2024-01-02
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
cobgdb does not seem to support user defined intrinsic functions or nested subprograms, they are skipped. Am i missing something?
Here is my test program.
I could not get b.cbl to compile. It had errors, so I made some changes. See BB.COB attached.
Also the call to hexDump had problem, so I included MY version called HEXDUMP to the bb.cob program.
It now produces;
61313233343541
nb = +00007
0x00dd8090
9080DD00
Program runs on 32-bit architecture.
Character set is ASCII.
Byte order is little endian
Dump of memory beginning at address: 0x00dd8090
Length of memory dump is: 7
Offset HEX-- -- -- -5 -- -- -- -- 10 -- -- -- -- 15 -- -- -- -- 20 -- -- -- -- 25 -- -- -- -- 30 -- -- CHARS----1----5----2----5----3--
000000 61 31 32 33 34 35 41 a12345A
Michael :-)
HEXDUMP.COB has a COPY book HEX-TAB.CPY.
Here it is attached.
Michael :-)
Last edit: Michael F Gleason 2024-01-02
Opps. I hit post twice by accident.
Michael :-)
Last edit: Michael F Gleason 2024-01-02
Sorry about that; i've sent the wrong source. My question was about the fact that ** cobgdb** does not seems to support user defined intrinsic functions and nested subprograms; they seems to be skipped. Am i wrong?
The main question for me is: Does it work with
cobcalone? In this case: yes, it does.So it is most reasonable to not post here but in the place where people discuss the development of cobgdb, that is https://github.com/marcsosduma/cobgdb/issues . As that software doesn't came out of nothing it would be interesting to know if issues you see with it are already part of its origin (in which both should be fixed) https://github.com/OlegKunitsyn/gnucobol-debug or are cobgdb-only (which also changes the way the developer would search for it).
In any case: be sure to post
cobc --versionas this makes a huge difference how the code is generated by cobc (which is "kind of reversed" with those extensions).Last edit: Mickey White 2024-01-02