#34 library unload error

closed
nobody
None
5
2009-03-29
2003-05-07
Anonymous
No

On 05/05/03, Jim Morcombe wrote:

> Is there a known problem with the "test15" program?
>
> I just compiled it and ran it. I gives me a
"Segmentation Error".
>
> It appears to have done everything correctly and then
falls
> over when it exits the program.
>
> If I put a DISPLAY statement immediately before the
STOP RUN,
> the DISPLAY statement is executed correctly, and then it
> crashes.

This problem appears to be on UN*X platform specific.

$gdb test15
GNU gdb 4.18
...
(gdb) r
main (test15) COB input :=====0:06:08:011:
sub (test15a) COB input :=====0:06:08:011:
sub (test15a) COB return :abcdef:12:16:022:
main (test15) COB return :abcdef:12:16:022:
main (test15) COB input :0=====:07:09:033:
sub (test15b) C input :0=====:07:09:033:
sub (test15b) C return :pqrsty:14:18:144:
main (test15) COB return :pqrsty:14:18:144:
main (test15) COB WS1=23:

Program received signal SIGSEGV, Segmentation fault.
0x804b665 in tcob_unload_runelement (element=0x805c6e0)
at general.c:471
471 tcob_close_real(files->file,NULL);
(gdb) ba
#0 0x804b665 in tcob_unload_runelement
(element=0x805c6e0) at general.c:471
#1 0x804b7dd in tcob_cancel_all () at general.c:539
#2 0x804ac4c in tcob_stop_run () at general.c:55
#3 0x8049689 in tinycobol_compiled. () at test15.cob:559
#4 0x400892e7 in __libc_start_main () from /lib/libc.so.6

From the GDB trace it appears that the TC run-time is
trying to unload
something which was not loaded in the first place,
since all sub-programs
are satirically linked.

Discussion

  • David Essex
    David Essex
    2009-03-29

    • status: open --> closed