From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org, roland@redhat.com
Subject: Re: [patch] build-id .debug files load (like .gnu_debuglink)
Date: Sat, 01 Sep 2007 12:15:00 -0000 [thread overview]
Message-ID: <uir6uvayc.fsf@gnu.org> (raw)
In-Reply-To: <20070901113530.GA30667@host0.dyn.jankratochvil.net> (message from Jan Kratochvil on Sat, 1 Sep 2007 13:35:30 +0200)
> Date: Sat, 1 Sep 2007 13:35:30 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: gdb-patches@sourceware.org, roland@redhat.com
>
> > . The objcopy commands shown in your patch seem to be relevant only
> > to the ``debug link'' method (at least that's what I understand
> > from the last objcopy command). If so, I think we should say what
> > are the corresponding commands for the ``debug ID'' method.
> > Likewise, if there are (or going to be) features in elfutils that
> > support ``debug ID'', I think we should mention them, as we do for
> > ``debug links'' now.
>
> ``debug ID'' gets included by `ld --build-id', therefore by `gcc
> -Wl,--build-id', it is still not default in FSF GCC. There are no specific
> splitting commands required (such as `objcopy --add-gnu-debuglink' for the
> former "debug link".
But the first command, the one to create the separate debug info file,
is still needed, right?
In any case, we should tell that these commands (or at least the last
one) is only needed for the debug-link method.
> --- gdb/NEWS 28 Aug 2007 19:57:11 -0000 1.236
> +++ gdb/NEWS 1 Sep 2007 11:29:43 -0000
> @@ -61,6 +61,9 @@ Windows and SymbianOS).
> * The GDB remote stub, gdbserver, now supports dynamic link libraries
> (DLLs) on Windows and Windows CE targets.
>
> +* GDB now supports a faster verification a .debug file matches its binary
^^^
"that" is missing here.
> +according to its build-id signature, if the signature present.
^^^
"if the signature is present", the "is" part is missing.
> +``Debug ID'' gets embedded into the main executable using @code{ld --build-id}
> +or the @value{NGCC} counterpart @code{gcc -Wl,--build-id}. ``Debug ID''
> +support plus compatibility fixes for debug files separation are present in
> +@sc{gnu} binary utilities (Binutils) since version 2.17.50.0.18.
This is fine, but there's no need to quote ``debug ID'' every time you
use it. I quoted it only when I used it as a name of a method of
embedding information about the debug file; in other cases I used it
without quotes.
Otherwise, these two patches are okay with me.
Thanks.
next prev parent reply other threads:[~2007-09-01 12:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-24 18:05 Jan Kratochvil
2007-08-24 18:20 ` Daniel Jacobowitz
2007-08-25 22:49 ` Jan Kratochvil
2007-08-25 23:58 ` Daniel Jacobowitz
2007-08-26 9:41 ` Jan Kratochvil
2007-08-31 9:38 ` Eli Zaretskii
2007-08-31 20:51 ` [patch approval?] " Jan Kratochvil
2007-08-31 21:12 ` Daniel Jacobowitz
2007-09-01 8:01 ` Eli Zaretskii
[not found] ` <20070901081934.GA31205@host0.dyn.jankratochvil.net>
2007-09-01 10:31 ` [patch] " Eli Zaretskii
2007-09-01 11:35 ` Jan Kratochvil
2007-09-01 12:15 ` Eli Zaretskii [this message]
2007-09-01 13:12 ` Jan Kratochvil
2007-09-01 13:25 ` Mark Kettenis
2007-09-01 14:22 ` Eli Zaretskii
2007-09-02 13:57 ` [patch approved?] [doc] " Jan Kratochvil
2007-09-02 17:49 ` Mark Kettenis
2007-09-02 19:38 ` Eli Zaretskii
2007-09-01 14:16 ` [patch] " Eli Zaretskii
2007-09-04 2:21 ` Roland McGrath
2007-09-04 3:23 ` Eli Zaretskii
2007-09-04 7:21 ` Roland McGrath
2007-09-15 9:52 ` Eli Zaretskii
2007-09-16 17:19 ` Roland McGrath
2007-08-25 22:48 ` Roland McGrath
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=uir6uvayc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=roland@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