The variable/expression panes should only be triggered for the COBOL sources.
Scenario attach - in this case it is very likely (actually: it always happens) that the process is in a "C" or "libcob" space. In this case cobcd-rw is called with an empty source, but should be called with the actual COBOL file.
Debug console:
No symbol table is loaded. Use the "file" command.
Attaching to process 15523
Reading symbols from /home/simon/test/petstore...
done.
Reading symbols from /lib64/libcob.so.4...
done.
Loaded symbols for /lib64/libcob.so.4
Reading symbols from /lib64/libm.so.6...
(no debugging symbols found)...done.
Loaded symbols for /lib64/libm.so.6
Reading symbols from /lib64/libc.so.6...
(no debugging symbols found)...done.
Loaded symbols for /lib64/libc.so.6
Reading symbols from /lib64/libgmp.so.10...
Reading symbols from /lib64/libgmp.so.10...
(no debugging symbols found)...done.
(no debugging symbols found)...done.
Loaded symbols for /lib64/libgmp.so.10
Reading symbols from /lib64/libncursesw.so.5...
Reading symbols from /lib64/libncursesw.so.5...
(no debugging symbols found)...done.
(no debugging symbols found)...done.
Loaded symbols for /lib64/libncursesw.so.5
Reading symbols from /lib64/libtinfo.so.5...
Reading symbols from /lib64/libtinfo.so.5...
(no debugging symbols found)...done.
(no debugging symbols found)...done.
Loaded symbols for /lib64/libtinfo.so.5
Reading symbols from /lib64/libdl.so.2...
(no debugging symbols found)...done.
Loaded symbols for /lib64/libdl.so.2
Reading symbols from /lib64/ld-linux-x86-64.so.2...
(no debugging symbols found)...done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
Not implemented stop reason (assuming exception): undefined
registering CPrint (Usage is "print <COBOL identifier>") [Version 3.10]
registering CWatch (Usage is "cwatch <COBOL identifier>")
No stack.
Traceback (most recent call last):
File "/opt/cbl-gdb-3.10/bin/cobcd.py", line 3158, in invoke
self.Worker.ProcessArguments(self.TabFile,GV_ShortTermMemory,arguments)
File "/opt/cbl-gdb-3.10/bin/cobcd.py", line 3040, in ProcessArguments
possibilities = MetaPossibilities(args,TabFile,ShortTermMemory,self.machine_interface_mode)
File "/opt/cbl-gdb-3.10/bin/cobcd.py", line 2833, in MetaPossibilities
return_string = subprocess.check_output(["cobcd-rw", TabFile.current_trapped_file, str(TabFile.current_trapped_line), str(TabFile.usual_suspects_range) ])
File "/usr/lib64/python2.7/subprocess.py", line 575, in check_output
raise CalledProcessError(retcode, cmd, output=output)
CalledProcessError: Command '['cobcd-rw', '', '0', '6']' returned non-zero exit status 1
The bad call to cobcd-rw
(according to the stack trace it should be Command '['cobcd-rw', '/home/simon/test/petstore.cbl', '80', '6']'
)
Stack trace and variable pane:
See cbl-gdb#5 (closed) for a minimal related issue.
Note: this one is a bit of a show stopper as it breaks the variable and watch pane :-(
Edited by Simon Sobisch