public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/4] Add DAP log level parameter
Date: Tue, 12 Dec 2023 20:39:08 +0200	[thread overview]
Message-ID: <838r5ztgdv.fsf@gnu.org> (raw)
In-Reply-To: <20231212-dap-no-test-exceptions-v1-2-af0e33f10093@adacore.com> (message from Tom Tromey on Tue, 12 Dec 2023 10:44:43 -0700)

> From: Tom Tromey <tromey@adacore.com>
> Date: Tue, 12 Dec 2023 10:44:43 -0700
> 
> This adds a new parameter to control the DAP logging level.  By
> default, "expected" exceptions are not logged, but the parameter lets
> the user change this when more logging is desired.
> 
> This also changes a couple of spots to avoid logging the stack trace
> for a DAPException.
> 
> This patch also documents the existing DAP logging parameter.  I
> forgot to document this before.
> ---
>  gdb/NEWS                             |  5 +++++
>  gdb/doc/gdb.texinfo                  | 18 ++++++++++++++++++
>  gdb/python/lib/gdb/dap/breakpoint.py |  6 ++++--
>  gdb/python/lib/gdb/dap/server.py     | 10 ++++++++++
>  gdb/python/lib/gdb/dap/startup.py    | 29 +++++++++++++++++++++++++----
>  5 files changed, 62 insertions(+), 6 deletions(-)

Thanks, the documentation parts are okay, with one comment:

> +@table @code
> +@item set debug dap-log-file @r{[}@var{filename}@r{]}
> +Enable DAP logging.  Logs are written to the specified file.  If no
> +file is given, logging is stopped.

I suggest to use "@var{filename}" instead of "file" here, on both
occasions.

Reviewed-By: Eli Zaretskii <eliz@gnu.org>

  reply	other threads:[~2023-12-12 18:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-12 17:44 [PATCH 0/4] Check for rogue DAP exceptions Tom Tromey
2023-12-12 17:44 ` [PATCH 1/4] Introduce and use DAPException Tom Tromey
2023-12-12 17:44 ` [PATCH 2/4] Add DAP log level parameter Tom Tromey
2023-12-12 18:39   ` Eli Zaretskii [this message]
2023-12-14 19:02     ` Tom Tromey
2023-12-13 16:35   ` Kévin Le Gouguec
2023-12-14 19:06     ` Tom Tromey
2023-12-12 17:44 ` [PATCH 3/4] Avoid exception from attach in DAP Tom Tromey
2023-12-13 16:36   ` Kévin Le Gouguec
2023-12-14 18:52     ` Tom Tromey
2023-12-12 17:44 ` [PATCH 4/4] Check for rogue DAP exceptions in test suite Tom Tromey
2023-12-13 16:36 ` [PATCH 0/4] Check for rogue DAP exceptions Kévin Le Gouguec
2023-12-22 16:57 ` 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=838r5ztgdv.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).