From: Tom Tromey <tom@tromey.com>
To: Akseli Lahtinen <akselmo@akselmo.dev>
Cc: Tom Tromey <tom@tromey.com>, gdb@sourceware.org
Subject: Re: Help with setting up DAP for Kate text editor
Date: Mon, 22 Jan 2024 06:45:19 -0700 [thread overview]
Message-ID: <877ck1lbww.fsf@tromey.com> (raw)
In-Reply-To: <3020567.otQIP8See3@fedora-desktop> (Akseli Lahtinen's message of "Sun, 21 Jan 2024 19:03:10 +0200")
>>>>> Akseli Lahtinen <akselmo@akselmo.dev> writes:
> Hey, sorry for the late response.
> I have requested an account to the sourceware bugzilla so I can
> create a separate bug report, but here's the logs I got from running the
> command.
Thank you. The problem seems clear to me:
> READ: <<<{"arguments": null, "command": "configurationDone", "seq": 2, "type":
> "request"}>>>
Here, 'arguments' is documented as:
interface ConfigurationDoneRequest extends Request {
command: 'configurationDone';
arguments?: ConfigurationDoneArguments;
}
In gdb, I assumed that optional things would simply not be provided. It
isn't clear to me that 'null' is a valid value here.
I filed an DAP clarification bug to find out:
https://github.com/microsoft/debug-adapter-protocol/issues/456
If this is in fact valid, it's easy to fix. I have a patch for it
already, but I'd prefer not to land it if this request is invalid.
Tom
next prev parent reply other threads:[~2024-01-22 13:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 9:24 Akseli Lahtinen
2024-01-17 15:15 ` Tom Tromey
2024-01-21 17:03 ` Akseli Lahtinen
2024-01-22 13:45 ` Tom Tromey [this message]
2024-01-22 17:21 ` Tom Tromey
2024-01-22 17:28 ` Akseli Lahtinen
2024-01-22 19:05 ` Tom Tromey
2024-01-22 21:07 ` Akseli Lahtinen
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=877ck1lbww.fsf@tromey.com \
--to=tom@tromey.com \
--cc=akselmo@akselmo.dev \
--cc=gdb@sourceware.org \
/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