Re: [PATCH] Initial implementation of Debugger Adapter Protocol

[Tom de Vries <tdevries@suse.de>]

On 1/2/23 17:54, Tom Tromey via Gdb-patches wrote:
>>>>>> "Tom" == Tom Tromey via Gdb-patches <gdb-patches@sourceware.org> writes:
> 
> Tom> The Debugger Adapter Protocol is a JSON-RPC protocol that IDEs can use
> Tom> to communicate with debuggers.  You can find more information here:
> 
> Tom> https://microsoft.github.io/debug-adapter-protocol/
> 
> Here is v4 of this patch.  This version updates the previous gdb
> exception handling some more, redirects stderr, fixes pending breakpoint
> handling, fixes the breakpoint event contents, and arranges to re-use
> existing breakpoints when possible.
> 
> The documentation hasn't changed at all.
> 
> Tom> More changes are on their way.  I suppose at some point, barring any
> Tom> comments, I will just check this in and switch to sending updates as
> Tom> regular patches.
> 
> I'm going to check in this version on the trunk.  Future work will be
> sent in the usual way.

I'm running into:
...
/home/vries/gdb_versions/devel/src/gdb/python/py-dap.c: In member 
function ‘virtual void dap_interp::init(bool)’:
/home/vries/gdb_versions/devel/src/gdb/python/py-dap.c:83:27: error: 
‘PyObject_CallNoArgs’ was not declared in this scope
    gdbpy_ref<> result_obj (PyObject_CallNoArgs (func.get ()));
                            ^~~~~~~~~~~~~~~~~~~
/home/vries/gdb_versions/devel/src/gdb/python/py-dap.c:83:27: note: 
suggested alternative: ‘_PyObject_CallNoArg’
    gdbpy_ref<> result_obj (PyObject_CallNoArgs (func.get ()));
                            ^~~~~~~~~~~~~~~~~~~
                            _PyObject_CallNoArg
...

Thanks,
- Tom