From: Eli Zaretskii <eliz@gnu.org>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] "info source" now includes producer string
Date: Mon, 05 Jan 2015 20:50:00 -0000 [thread overview]
Message-ID: <838uhh7y0t.fsf@gnu.org> (raw)
In-Reply-To: <yjt2h9w52c4v.fsf@ruffy.mtv.corp.google.com>
> From: Doug Evans <dje@google.com>
> Date: Mon, 05 Jan 2015 12:41:52 -0800
>
> bash$ g++ -g -Og hello.cc -o hello
> bash$ gdb hello
> (gdb) start
> (gdb) info source
> Current source file is hello.cc
> Compilation directory is /home/dje
> Located in /home/dje/hello.cc
> Contains 8 lines.
> Source language is c++.
> Producer is GNU C++ 4.8.2 -mtune=generic -march=x86-64 -g -Og -fstack-protector.
> Compiled with DWARF 2 debugging format.
> Does not include preprocessor macro info.
Thanks.
> * NEWS: "info source" command now display producer string if present.
^^^^^^^
"displays"
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -113,6 +113,9 @@ VAX running Ultrix vax-*-ultrix*
> and "assf"), have been removed. Use the "sharedlibrary" command, or
> its alias "share", instead.
>
> +* The "info source" command now displays the producer string if it was
> + present in the debug info.
I wonder whether we should replace "producer" with something less
abstract. Would "compilation command line" be accurate enough?
> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -16279,6 +16279,8 @@ its length, in lines,
> @item
> which programming language it is written in,
> @item
> +if the debug information provides it, the program that compiled the file,
Not just the program, but also its command line, right?
Okay with those fixed.
next prev parent reply other threads:[~2015-01-05 20:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 20:41 Doug Evans
2015-01-05 20:50 ` Eli Zaretskii [this message]
2015-01-06 0:28 ` Doug Evans
2015-01-06 3:31 ` Eli Zaretskii
2015-01-31 22:29 ` Doug Evans
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=838uhh7y0t.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dje@google.com \
--cc=gdb-patches@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: 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).