Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: handle "MiniDebuginfo" section
Date: Tue, 13 Nov 2012 19:12:00 -0000	[thread overview]
Message-ID: <50A29B8B.7050606@redhat.com> (raw)
In-Reply-To: <877gpp8i67.fsf@fleche.redhat.com>

On 11/13/2012 06:35 PM, Tom Tromey wrote:
> index 86cfe8e..d04566e 100644
> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -15865,6 +15865,7 @@ program.  To debug a core dump of a previous run, you must also tell
>  @menu
>  * Files::                       Commands to specify files
>  * Separate Debug Files::        Debugging information in separate files
> +* Separate Debug Section::      Debugging information in a special section

This is likely a very minor issue, but, on "Separate Debug Section":  I understand
that "Separate" came from this being a reuse of the "separate debug file" idea,
but OTOH I find that terminology confusing (which makes me think first-time
readers unaware of the concept might too on first grance).  The debug info is
is actually bolted inside the main binary, which is the opposite of
separate.  :-)  Maybe:

"Debug File Embedded in Special Section"

"Separate Debug File Embedded in Special Section"

Are we going to call this "MiniDebugInfo" going forward (as the minidebug.c
file spells it)?  Would it be a good idea to put a "a.k.a. MiniDebugInfo"
in the docs?

>  * Index Files::                 Index files speed up GDB
>  * Symbol Errors::               Errors reading symbol files
>  * Data Files::                  GDB data files


On 11/13/2012 06:35 PM, Tom Tromey wrote:
> +if {[is_remote host]} {
> +    return 0
> +}

This is no longer necessary.

Otherwise I have no further comments.  Thanks.

-- 
Pedro Alves


  parent reply	other threads:[~2012-11-13 19:12 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-09 17:33 Tom Tromey
2012-11-09 18:07 ` Eli Zaretskii
2012-11-09 18:13 ` Pedro Alves
2012-11-09 21:28   ` Tom Tromey
2012-11-13 12:56     ` Pedro Alves
2012-11-13 15:26       ` Pedro Alves
2012-11-13 18:32       ` Tom Tromey
2012-11-09 18:23 ` Joel Brobecker
2012-11-09 18:53   ` Pedro Alves
2012-11-09 19:13   ` Tom Tromey
2012-11-12 16:04   ` Tom Tromey
2012-11-12 17:04     ` Joel Brobecker
2012-11-12 18:24       ` Tom Tromey
2012-11-12 16:28 ` Tom Tromey
2012-11-13 18:36   ` Tom Tromey
2012-11-13 18:42     ` Eli Zaretskii
2012-11-13 19:12     ` Pedro Alves [this message]
2012-11-13 20:57       ` Tom Tromey
2012-11-14 16:13         ` Tom Tromey
2012-11-14 16:19           ` Pedro Alves
2012-11-14 16:59             ` Tom Tromey
2012-11-14 19:37           ` Doug Evans
2012-11-14 22:12             ` Joel Brobecker
2012-11-15 11:18             ` Pedro Alves
2012-11-16 19:51               ` Tom Tromey
2012-11-19 14:41                 ` Pedro Alves
2012-11-26 19:21                   ` Tom Tromey
2012-11-26 22:24                     ` Andrew Pinski
2012-11-27  2:23                       ` Tom Tromey
2012-11-29 19:19                     ` Ulrich Weigand
2012-11-29 19:23                       ` Tom Tromey
2012-11-29 19:33                         ` Ulrich Weigand
2012-11-29 20:51                           ` Tom Tromey
2012-11-30 14:05                             ` Ulrich Weigand
2012-11-30 20:59                               ` Tom Tromey
2012-12-05 17:09                                 ` Ulrich Weigand
2012-12-11 16:42                     ` Yufeng Zhang
2012-11-16 20:04             ` Tom Tromey
2012-11-12 21:26 ` Doug Evans
2012-11-13 17:43   ` Tom Tromey
2012-11-13 15:44 ` Jan Kratochvil
2012-11-13 18:34   ` Tom Tromey

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=50A29B8B.7050606@redhat.com \
    --to=palves@redhat.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