From: Oleg Tolmatcev <oleg.tolmatcev@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v4] gdb/dap: add option commandEscapePrefix
Date: Sun, 16 Nov 2025 15:33:04 +0100 [thread overview]
Message-ID: <CACcXsZhTkgccWx3=Us3koXyfjJ6qHM9J9y0mvpM8dg2Tgba6KQ@mail.gmail.com> (raw)
In-Reply-To: <865xbam4ku.fsf@gnu.org>
Am So., 16. Nov. 2025 um 15:31 Uhr schrieb Eli Zaretskii <eliz@gnu.org>:
>
> > From: oltolm <oleg.tolmatcev@gmail.com>
> > Cc: oltolm <oleg.tolmatcev@gmail.com>
> > Date: Sun, 16 Nov 2025 15:26:14 +0100
> >
> > The escape prefix to use for executing regular GDB commands in the Debug
> > Console, instead of printing variables. Defaults to an empty string. If it's
> > an empty string, then all expressions in the Debug Console are treated as
> > regular GDB commands.
> >
> > Signed-off-by: oltolm <oleg.tolmatcev@gmail.com>
> > ---
> > gdb/doc/gdb.texinfo | 6 ++++++
> > gdb/python/lib/gdb/dap/completions.py | 15 ++++++++++++---
> > gdb/python/lib/gdb/dap/evaluate.py | 15 ++++++++++++---
> > gdb/python/lib/gdb/dap/launch.py | 5 +++++
> > gdb/python/lib/gdb/dap/server.py | 14 ++++++++++++++
> > 5 files changed, 49 insertions(+), 6 deletions(-)
>
> Thanks. I already approved the gdb.texinfo part of v3, but I also
> asked whether this warrants an entry in NEWS.
Sorry, I don't know.
> Reviewed-By: Eli Zaretskii <eliz@gnu.org>
next prev parent reply other threads:[~2025-11-16 14:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-16 14:26 oltolm
2025-11-16 14:31 ` Eli Zaretskii
2025-11-16 14:33 ` Oleg Tolmatcev [this message]
2025-11-16 15:03 ` Eli Zaretskii
2025-11-19 18:52 ` Tom Tromey
2025-11-19 18:54 ` Tom Tromey
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='CACcXsZhTkgccWx3=Us3koXyfjJ6qHM9J9y0mvpM8dg2Tgba6KQ@mail.gmail.com' \
--to=oleg.tolmatcev@gmail.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@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