public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Roland McGrath <roland@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Panu Matilainen <pmatilai@redhat.com>,
	Project Archer <archer@sourceware.org>
Subject: Re: find-debuginfo.sh change for gdb index
Date: Tue, 06 Jul 2010 20:28:00 -0000	[thread overview]
Message-ID: <20100706202828.8ABFA4824F@magilla.sf.frob.com> (raw)
In-Reply-To: Tom Tromey's message of  Tuesday, 6 July 2010 13:41:41 -0600 <m3wrt8bdoq.fsf@fleche.redhat.com>

> I was thinking we would just objcopy the data into the .debug file in
> find-debuginfo.sh.
> 
> Is there an advantage to doing it before the stripping?

I stated two:

1. CRC32 in .gnu_debuglink will be correct.
   
2. Do it to those that don't get stripped.  
   (AFAIK the only case is vmlinux.)

I am not especially concerned about either of those issues.  But they point
to it probably being the more right or more clean approach.

I am far more concerned about the unknown potential problems.
For example, making sure that eu-unstrip can still recombine the files.
(I think that will be fine, but it's something to worry about.)

In the past we have had various problems with objcopy/bfd deciding to
gratuitously regenerate things and breaking the data along the way.
I believe all the old issues we ever noticed have been fixed by now.
But it certainly makes me nervous.  I trust eu-strip far more.


Thanks,
Roland

  reply	other threads:[~2010-07-06 20:28 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-29 22:32 Tom Tromey
2010-06-29 23:21 ` Roland McGrath
2010-06-30 17:35   ` Tom Tromey
2010-06-30 18:14     ` Roland McGrath
2010-06-30 18:23       ` Tom Tromey
2010-06-30 20:42         ` Tom Tromey
2010-06-30 20:44           ` Roland McGrath
2010-06-30 21:25             ` Tom Tromey
2010-06-30 21:58               ` Tom Tromey
2010-06-30 22:00                 ` Tom Tromey
2010-06-30 22:14               ` Roland McGrath
2010-07-02 19:55                 ` Tom Tromey
2010-07-05  9:36                   ` Panu Matilainen
2010-07-05  9:48                     ` Jan Kratochvil
2010-07-05 10:39                       ` Panu Matilainen
2010-07-06 18:35                     ` Tom Tromey
2010-07-06 19:14                       ` Roland McGrath
2010-07-06 19:41                         ` Tom Tromey
2010-07-06 20:28                           ` Roland McGrath [this message]
2010-07-08 15:56                         ` Tom Tromey
2010-07-08 20:36                           ` Tom Tromey
2010-07-08 22:53                           ` Roland McGrath
2010-07-09  5:07                             ` Panu Matilainen
2010-07-09 17:48                               ` Tom Tromey
2010-07-30 21:36                                 ` Tom Tromey
2010-07-30 23:07                                   ` Roland McGrath
2010-07-30 23:09                                   ` 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=20100706202828.8ABFA4824F@magilla.sf.frob.com \
    --to=roland@redhat.com \
    --cc=archer@sourceware.org \
    --cc=pmatilai@redhat.com \
    --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).