From: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
To: Tom Tromey <tromey@adacore.com>,
Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Initial implementation of Debugger Adapter Protocol
Date: Tue, 3 Jan 2023 09:04:17 +0100 [thread overview]
Message-ID: <5cd9edba-b1b2-060e-d8d2-98ff6d28a5e7@suse.de> (raw)
In-Reply-To: <87k024khch.fsf@tromey.com>
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
next prev parent reply other threads:[~2023-01-03 8:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 16:30 Tom Tromey via Gdb-patches
2022-09-01 16:38 ` Eli Zaretskii via Gdb-patches
2022-09-12 19:54 ` Tom Tromey via Gdb-patches
2022-09-13 2:26 ` Eli Zaretskii via Gdb-patches
2022-10-06 14:27 ` Tom Tromey via Gdb-patches
2023-01-02 16:54 ` Tom Tromey via Gdb-patches
2023-01-03 8:04 ` Tom de Vries via Gdb-patches [this message]
2023-01-03 14:14 ` Tom Tromey via Gdb-patches
2023-01-04 11:59 ` Tom de Vries via Gdb-patches
2023-01-04 12:27 ` Tom de Vries via Gdb-patches
2023-01-05 9:49 ` [PATCH] [gdb/python] Avoid queue.SimpleQueue for python 3.6 Tom de Vries via Gdb-patches
2023-01-05 15:19 ` Tom Tromey via Gdb-patches
2023-01-05 16:34 ` Tom de Vries via Gdb-patches
2023-01-05 17:07 ` Tom Tromey via Gdb-patches
2023-01-05 11:35 ` [PATCH] Initial implementation of Debugger Adapter Protocol Tom de Vries via Gdb-patches
2023-01-05 15:24 ` Tom Tromey via Gdb-patches
2023-01-05 16:17 ` Tom de Vries via Gdb-patches
2023-01-06 14:12 ` Tom de Vries via Gdb-patches
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5cd9edba-b1b2-060e-d8d2-98ff6d28a5e7@suse.de \
--to=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
--cc=tromey@adacore.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox