From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org, hal9000ed2k@gmail.com
Subject: Re: [patchv2] GDB 7.2: new feature for "backtrace" that cuts path to file (remain filename)
Date: Fri, 30 Nov 2012 20:22:00 -0000 [thread overview]
Message-ID: <83lidiu9im.fsf@gnu.org> (raw)
In-Reply-To: <20121130185653.GA15394@host2.jankratochvil.net>
> Date: Fri, 30 Nov 2012 19:56:53 +0100
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: Eldar Gaynetdinov <hal9000ed2k@gmail.com>
>
> starting a new thread, formerly it was:
> Re: [patch] GDB 7.2: new feature for "backtrace" that cuts path to file (remain filename)
> Message-ID: <20120406142114.GA25129@host2.jankratochvil.net>
> http://sourceware.org/ml/gdb-patches/2012-04/msg00106.html
Thanks.
> +set backtrace filename-display basename|relative|absolute
> +show backtrace filename-display
> + Control the way in which filenames is displayed in backtraces.
> + The default remains unchanged ("relative").
The default cannot "remain" because this setting was not in GDB
before. So 'The default is "relative".' is a better wording.
> +If backtraces aren't easy to read due to a long absolute filename record and
> +you just want to see only a basename or a relative filename,
> +you can change this behavior:
The current behavior, and the default one after this change, is to
show relative file names, so talking about long absolute file names is
confusing. I would say something simpler, like
You can control how file names are displayed in backtraces.
> +@itemx set backtrace filename-display relative
> +@cindex backtrace filename-display
> +Display a filename without the compilation directory part.
"A file name without the directory" can be easily be interpreted as
basename. I suggest
Display file names relative to the compilation directory.
> +@item show backtrace filename-display
> +Show the current way to display a filename in backtraces.
^^^^^^^^^^
"filenames", in plural.
The documentation parts are OK with these changes.
> + add_setshow_enum_cmd ("filename-display", class_obscure,
> + filename_display_kind_names,
> + &filename_display_string, _("\
> +Set how to display filenames in backtraces."), _("\
> +Show how to display filenames in backtraces."), _("\
> +filename-display can be:\n\
> + basename - display only basename of a filename\n\
> + relative - display a filename without the compilation directory part\n\
Here, too, I'd say "relative to the compilation directory."
> + absolute - display an absolute filename\n\
> +By default, as-recorded filename is displayed."),
The last sentence seems to imply that the default is different from
"relative", and once changed to something else, cannot be restored,
since none of the settings is the default. But the truth is that the
default is "relative", right?
next prev parent reply other threads:[~2012-11-30 20:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-30 18:57 Jan Kratochvil
2012-11-30 20:22 ` Eli Zaretskii [this message]
2012-12-01 17:28 ` Jan Kratochvil
2012-12-01 17:33 ` Eli Zaretskii
2012-12-01 17:55 ` Jan Kratochvil
2012-12-05 21:38 ` Tom Tromey
2012-12-06 10:04 ` Jan Kratochvil
2012-11-30 23:09 ` iam ahal
2012-12-01 17:15 ` Jan Kratochvil
2012-12-02 16:39 ` iam ahal
2012-12-03 10:11 ` Andrew Burgess
2012-12-03 13:21 ` Jan Kratochvil
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=83lidiu9im.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=hal9000ed2k@gmail.com \
--cc=jan.kratochvil@redhat.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