Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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 14:16:00 -0000	[thread overview]
Message-ID: <uhcmev5ca.fsf@gnu.org> (raw)
In-Reply-To: <20070901131212.GA32719@host0.dyn.jankratochvil.net> (message 	from Jan Kratochvil on Sat, 1 Sep 2007 15:12:12 +0200)

> Date: Sat, 1 Sep 2007 15:12:12 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: gdb-patches@sourceware.org, roland@redhat.com
> 
> On Sat, 01 Sep 2007 14:15:07 +0200, Eli Zaretskii wrote:
> ...
> > 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.
> 
> Enhanced the section I hope according to your advice.

Thanks, this is okay.

> +foo.debug} has the same functionality as the two separating commands and the
> +one linking command above.

I'd suggest to rewrite this as follows:

 +foo.debug} has the same functionality as the two @code{objcopy} commands
 +and the @code{ln -s} command above, together.


  parent reply	other threads:[~2007-09-01 14:16 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
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                     ` Eli Zaretskii [this message]
2007-09-04  2:21                   ` [patch] " 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=uhcmev5ca.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