From: Eli Zaretskii <eliz@gnu.org>
To: dje@google.com (Doug Evans)
Cc: tromey@redhat.com, gdb-patches@sourceware.org
Subject: Re: [patch] gdb-add-index tweaks
Date: Fri, 03 Sep 2010 22:07:00 -0000 [thread overview]
Message-ID: <83hbi6ite0.fsf@gnu.org> (raw)
In-Reply-To: <20100903180117.42E9D841F7@ruffy.mtv.corp.google.com>
> Date: Fri, 3 Sep 2010 11:01:17 -0700 (PDT)
> From: dje@google.com (Doug Evans)
>
> This patch makes gdb-add-index.sh a (teensy) bit more robust
> and restores the Makefile.in/gdb.texinfo changes (the latter with
> a few tweaks).
Thanks.
> @@ -15230,8 +15230,8 @@ This computation does not apply to the `
> When @value{GDBN} finds a symbol file, it scans the symbols in the
> file in order to construct an internal symbol table. This lets most
> @value{GDBN} operations work quickly---at the cost of a delay early
> -on. For large programs, this delay can be quite lengthy, so
> -@value{GDBN} provides a way to build an index, which speeds up
> +on. For large programs this delay can be quite lengthy, so
> +@value{GDBN} provides a way to build an index which speeds up
> startup.
I see no reason for this hunk of changes. There's nothing wrong with
the original text.
> There are currently some limitation on indices. They only work when
> -for DWARF debugging information, not stabs. And, they do not
> -currently work for programs using Ada.
> +using DWARF debugging information, not stabs. And, they do not
> +currently work for programs written in Ada.
This is okay, but I would lose the "not stabs" part, because we
support more than just DWARF and stabs. I understand that only DWARF
will enable this feature.
> +@value{GDBN} comes with a program, @command{gdb-add-index}, which can
> +be used to add the index to a symbol file. It takes the symbol file
> +as its only argument:
We don't really explain what is a "symbol file". But I guess this is
a problem with this entire chapter; feel free to fix that or leave it
as it is now.
> +@command{gdb-add-index} is a simple script, with minimal error checking.
If it's a script, why we say above that it's a program?
next prev parent reply other threads:[~2010-09-03 18:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 18:27 Doug Evans
2010-09-03 22:07 ` Eli Zaretskii [this message]
2010-09-04 13:45 ` Tom Tromey
2010-11-16 7:46 ` Jan Kratochvil
2010-11-16 17:27 ` Tom Tromey
2010-11-16 17:38 ` Tom Tromey
2010-09-06 9:48 ` 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=83hbi6ite0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).