meerkut

Simon> PROCEDURE DIVISION USING (in this - most common - case, it gets the address of what the caller passed in this position; which may include the cases "nothing", OMITTED, a variable that also has no address, a variable that has not enough space or a totally different USAGE) ENTRY xyz USING (similar to the first) SET ADDRESS OF V1 TO ... (no change for the data size or content either) ALLOCATE V1 So "in general" it is no problem that a field in LINKAGE is not in PROCEDURE DIVISION USING. Absolutely...

Let us demonstrate that statement A: "the phrase 'USING V1' is optional in the syntax of the program for gnuCOBOL" is incorrect. Assuming the phrase 'USING V1' is optional, similar to words like IS or BY, the gnuCOBOL compiler should consistently assign a valid V1 address based solely on the information in the "LINKAGE" section. Moreover, if the address of V1 is assigned, it must not be NULL. However, the compilation result indicates that the address of V1 is NULL. If we do not negate 1, 2, and 3,...

Simon, when a bug can be identified without needing to run the compiled program, and a static examination of the code is sufficient, it indicates a compiler failure.

the compiler's lack of USING phrase check for the PROC.DIV. leads to a segfault

Chuck, Here is the output: $ cobc --info cobc (GnuCOBOL) 3.1.2.0 Copyright (C) 2020 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html> This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Written by Keisuke Nishida, Roger While, Ron Norman, Simon Sobisch, Edward Hart Built Jun 16 2023 04:35:55 Packaged Dec 23 2020 12:04:58 UTC C version "10.2.1...

I want to clarify that this error is not related to my demonstration code, which was specifically designed to showcase that there exists a byte sequence indicating a breakdown in the GNUCOBOL compiler's logic. This error is of utmost importance as it causes a complete the GNUCOBOL compiler crash. The issue at hand is as follows: when providing input data that contains "garbage" or incorrect values, the program unexpectedly terminates. Just for fun -- comment out, say, Line 19, in my demonstration...

attempt to reference unallocated memory

Hello, Japheth! JWasm v2.11, Oct 20 2013 JWlink Version 1.9beta 13 When I use externdef...