public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tom de Vries <tdevries@suse.de>
Cc: tom@tromey.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/symtab] Add set/show always-read-ctf on/off
Date: Thu, 02 Mar 2023 11:38:03 +0200	[thread overview]
Message-ID: <83o7pbebno.fsf@gnu.org> (raw)
In-Reply-To: <39e29bc3-bdeb-2a7e-3760-39ffe673308b@suse.de> (message from Tom de Vries on Thu, 2 Mar 2023 08:18:45 +0100)

> Date: Thu, 2 Mar 2023 08:18:45 +0100
> Cc: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
> From: Tom de Vries <tdevries@suse.de>
> 
> diff --git a/gdb/NEWS b/gdb/NEWS
> index bea604d7e75..c32ff92c98a 100644
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -68,6 +68,11 @@ maintenance info frame-unwinders
>    List the frame unwinders currently in effect, starting with the highest
>    priority.
>  
> +set always-read-ctf on|off
> +show always-read-ctf
> +  When off, CTF is only read if DWARF is not present.  When on, CTF is
> +  read regardless of whether DWARF is present.  Off by default.
> +
>  * New convenience function "$_shell", to execute a shell command and
>    return the result.  This lets you run shell commands in expressions.
>    Some examples:

This part is OK.

> diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
> index c1ca45521ea..85fe2158ce8 100644
> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -20365,6 +20365,15 @@ location to represent a line or a statement.  The @samp{PROLOGUE-END} column
>  indicates that a given address is an adequate place to set a breakpoint at the
>  first instruction following a function prologue.
>  
> +@kindex set always-read-ctf [on|off]
> +@kindex show always-read-ctf
> +@cindex always-read-ctf

I'd add a @cindex entry that begins with CTF, something like

  @cindex CTF info, when to read

> +When off, CTF is only read if DWARF is not present.  When on, CTF is
> +read regardless of whether DWARF is present.  The default value if off.

It's probably "CTF debug info" and "DWARF debug info", right?

Thanks.

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

  reply	other threads:[~2023-03-02  9:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-24 12:35 Tom de Vries
2023-02-24 19:33 ` Tom Tromey
2023-02-25  8:42   ` Tom de Vries
2023-02-25 12:34     ` Tom Tromey
2023-02-26  8:25       ` Tom de Vries
2023-03-02  1:56         ` Tom Tromey
2023-03-02  7:18           ` Tom de Vries
2023-03-02  9:38             ` Eli Zaretskii [this message]
2023-03-02  9:58               ` Tom de Vries

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=83o7pbebno.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=tdevries@suse.de \
    --cc=tom@tromey.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).