cbl-gdb merge requestshttps://gitlab.cobolworx.com/COBOLworx/cbl-gdb/-/merge_requests2023-04-28T09:42:12Zhttps://gitlab.cobolworx.com/COBOLworx/cbl-gdb/-/merge_requests/159fix the python interpreter replacement on `make install`2023-04-28T09:42:12ZSimon Sobischfix the python interpreter replacement on `make install`by ignoring the version number that sometimes get changed in cobcd for whatever reasonby ignoring the version number that sometimes get changed in cobcd for whatever reasonhttps://gitlab.cobolworx.com/COBOLworx/cbl-gdb/-/merge_requests/153Draft: Exception handling, comma, enumerate2022-02-26T05:41:07ZSjaak WestdijkDraft: Exception handling, comma, enumeratehttps://gitlab.cobolworx.com/COBOLworx/cbl-gdb/-/merge_requests/121WIP: range checking according to GDB rules2021-10-28T10:41:17ZSimon SobischWIP: range checking according to GDB rulesimplementing #53
additional: follow-up to 79487a8ff0aaf10cd97732642b2048ff6887768d more ConditionalRaiseimplementing #53
additional: follow-up to 79487a8ff0aaf10cd97732642b2048ff6887768d more ConditionalRaisehttps://gitlab.cobolworx.com/COBOLworx/cbl-gdb/-/merge_requests/97WIP: ProcessStack and read-in of VARIABLE_STRING via gdb api2021-11-04T17:12:09ZSimon SobischWIP: ProcessStack and read-in of VARIABLE_STRING via gdb api* fixing #58: remove parsing of stack and frame via GDB user-output (which will be broken if any frame-filters are active)
* source-name suffix for VARIABLE_STRING read in from cob_module->module_source (this is what cobcd has seen, a l...* fixing #58: remove parsing of stack and frame via GDB user-output (which will be broken if any frame-filters are active)
* source-name suffix for VARIABLE_STRING read in from cob_module->module_source (this is what cobcd has seen, a later rename could otherwise break it - and we don't need to parse the frames)
* included suggested variant for using the program_id for the suffix instead
* VARIABLE_STRING read in by gdb api (single invocation instead of parsing and concatenating memory dumps)
replaces !86; WIP as it does not pass all testshttps://gitlab.cobolworx.com/COBOLworx/cbl-gdb/-/merge_requests/91internal handling for STOP RUN and runtime errors2021-06-10T13:50:07ZSimon Sobischinternal handling for STOP RUN and runtime errorsrelated to #47
@rdubner Please specify if we need a new parameter related to "stop before exit" or not. If the answer is "yes" then this possibly has to be set in the testsscripts (or via Makefile), if not then the test expectations (at...related to #47
@rdubner Please specify if we need a new parameter related to "stop before exit" or not. If the answer is "yes" then this possibly has to be set in the testsscripts (or via Makefile), if not then the test expectations (at the end and before "restart") have to be adjustedhttps://gitlab.cobolworx.com/COBOLworx/cbl-gdb/-/merge_requests/39WIP: disabled core part for completion performance2021-07-03T12:21:22ZSimon SobischWIP: disabled core part for completion performanceThe question is: do we really need that check here in general any more?
If we need it I suggest to add a new parameter to this function and only test that depending on the context.
The test would only be reasonable if:
* we want t...The question is: do we really need that check here in general any more?
If we need it I suggest to add a new parameter to this function and only test that depending on the context.
The test would only be reasonable if:
* we want to get the data
* we already have checked that the limit is not exceeded (so first gather only the possibilities, then resolve them next)