From: Eli Zaretskii <eliz@gnu.org>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: simon.marchi@ericsson.com, gdb-patches@sourceware.org
Subject: Re: [PATCH v2 4/4] Add doc and news for DWARF index cache
Date: Mon, 30 Jul 2018 19:23:00 -0000 [thread overview]
Message-ID: <83fu00plxz.fsf@gnu.org> (raw)
In-Reply-To: <77255cf544dd62fdd4878c03bbae5632@polymtl.ca> (message from Simon Marchi on Mon, 30 Jul 2018 15:04:43 -0400)
> Date: Mon, 30 Jul 2018 15:04:43 -0400
> From: Simon Marchi <simon.marchi@polymtl.ca>
> Cc: Simon Marchi <simon.marchi@ericsson.com>, gdb-patches@sourceware.org
>
> >> +@item show index-cache stats
> >> +Print the number of cache hits and misses for the index cache since
> >> the launch
> >> +of @value{GDBN}.
> >
> > This begs the question: for which index cache will this show the
> > statistics? For the one defined by the latest "set index-cache
> > directory" command?
>
> Ah, no it's dumber than that. It's just how many hits and misses there
> were since GDB was launched, regardless of the cache directory used.
> Perhaps it would be clearer to keep it short like:
>
> Print the number of cache hits and misses since the launch of
> @value{GDBN}.
>
> ?
Yes, that's better.
next prev parent reply other threads:[~2018-07-30 19:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-25 22:47 [PATCH v2 0/4] Add a " Simon Marchi
2018-07-25 22:47 ` [PATCH v2 4/4] Add doc and news for " Simon Marchi
2018-07-27 8:50 ` Eli Zaretskii
2018-07-30 19:04 ` Simon Marchi
2018-07-30 19:23 ` Eli Zaretskii [this message]
2018-07-25 22:47 ` [PATCH v2 2/4] Introduce mmap_file function Simon Marchi
2018-07-25 22:48 ` [PATCH v2 3/4] Add DWARF index cache Simon Marchi
2018-07-27 9:06 ` Eli Zaretskii
2018-07-27 14:01 ` Simon Marchi
2018-07-27 21:25 ` Eli Zaretskii
2018-07-30 15:33 ` Simon Marchi
2018-07-30 15:45 ` Simon Marchi
2018-07-30 15:57 ` Eli Zaretskii
2018-07-30 17:05 ` Simon Marchi
2018-07-25 22:48 ` [PATCH v2 1/4] Make index reading functions more modular Simon Marchi
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=83fu00plxz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.com \
--cc=simon.marchi@polymtl.ca \
/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).