public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "asmwarrior at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/15150] New: suggestion on adding some statements/words about how file names are displayed. Date: Fri, 15 Feb 2013 15:14:00 -0000 [thread overview] Message-ID: <bug-15150-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=15150 Bug #: 15150 Summary: suggestion on adding some statements/words about how file names are displayed. Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb AssignedTo: unassigned@sourceware.org ReportedBy: asmwarrior@gmail.com Classification: Unclassified Hi, with the change several days ago, I see some texts were added in the gdb manual to tell the user about changing how file names are displayed. gdb/doc/gdb.texinfo | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index a8a7284..a448c97 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -6535,6 +6535,24 @@ unlimited. Display the current limit on backtrace levels. @end table +You can control how file names are displayed. + +@table @code +@item set filename-display +@itemx set filename-display relative +@cindex filename-display +Display file names relative to the compilation directory. This is the default. + +@item set filename-display basename +Display only basename of a filename. + +@item set filename-display absolute +Display an absolute filename. + +@item show filename-display +Show the current way to display filenames. +@end table + @node Selection @section Selecting a Frame These changes were under the frame/backtrace section of the manual, but those options were in-fact affect on other part of the command response. E.g. the breakpoint command response. E.g.: set filename-display absolute will affect the result. [debug]> break "E:/code/cb/test_code/mortenr2012-01-15/main.cpp:16" [debug]Breakpoint 2 at 0x4016ef: file E:\code\cb\test_code\mortenr2012-01-15\main.cpp, line 16. So, please mention or add some texts for this kind of information. Thanks. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2013-02-15 15:14 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-02-15 15:14 asmwarrior at gmail dot com [this message] 2013-02-16 8:44 ` [Bug gdb/15150] " jan.kratochvil at redhat dot com
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=bug-15150-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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: linkBe 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).