https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119377
--- Comment #11 from Robert Dubner <rdubner at gcc dot gnu.org> ---
I am not surprised. When I first read about it a couple of days ago, it looked
to me like two separate problems.
Primus: We talked casually about my working with you to duplicate the working
environment on my Mac Mini. Is that something we can attempt?
Secundus: There is a magic thing you can do that might...might!...give Jim and
me some more information to work with, seeing as how without a working
environment we have to work by remote control like this.
I am assuming you can launch a compilation of that particular source code file.
When you do, set the GCOBOL_SHOW environment variable to anything:
GCOBOL_SHOW=1 gcobol declarative_1.cob
The basic structure of the COBOL front end is that Jim's parsing code figures
out what the programmer wants done, and the parser calls my target-code
generating routines, which mostly are named "parser_<this>" and
"parser_<that>".
The GCOBOL_SHOW environment variable causes many of those parser_<xxx> routines
to output that they have been called, and for many of them there is feedback
about what variables they were passed.
It's quite noisy, but sometimes invaluable. And in this case, it'll probably
give us some idea of exactly where things are going south.
