public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: perl-5.14.4
Date: Mon, 09 Feb 2015 17:16:00 -0000	[thread overview]
Message-ID: <87vbjbuhtf.fsf@Rainer.invalid> (raw)
In-Reply-To: <20150209102529.GH28033@calimero.vinschen.de> (Corinna Vinschen's	message of "Mon, 9 Feb 2015 11:25:29 +0100")

Corinna Vinschen writes:
> I think it's important to keep the information in sync while building
> the packages.  A later rebase will break the connection between debug
> symbols and runtime symbols as well, obviously.

Obviously?  I have no indication that the debug information is damaged
once it's been stripped off into a separate file.  Which may be a hint
on what rebase might do wrong.

> Maybe we should think of rebasing the actual binaries as well as their
> debugging counterparts to keep everything in sync, but that's a bit
> much effort...

I may not understand what is really going on, but the way I see it,
rebase does exactly that while the debug information is still part of
the object file.  It seems to do something extra or wrong, since objcopy
will the not be able to copy out that information.  Looking with objdump
reveals the section is still there ans has contents, but it doesn't get
associated with the code in the correct manner anymore.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf Blofeld V1.15B11:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

  reply	other threads:[~2015-02-09 17:16 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-04 20:41 perl-5.14.4 Achim Gratz
2015-02-04 21:57 ` perl-5.14.4 David Stacey
2015-02-04 22:10   ` perl-5.14.4 Achim Gratz
2015-02-05 17:57     ` perl-5.14.4 Reini Urban
2015-02-05 19:16       ` perl-5.14.4 Achim Gratz
2015-02-05  8:49 ` perl-5.14.4 Corinna Vinschen
2015-02-05 16:13 ` perl-5.14.4 Achim Gratz
2015-02-05 17:53   ` perl-5.14.4 Reini Urban
2015-02-05 19:13     ` perl-5.14.4 Achim Gratz
2015-02-06 19:22 ` perl-5.14.4 Achim Gratz
2015-02-08 20:19   ` perl-5.14.4 Achim Gratz
2015-02-09 10:25     ` perl-5.14.4 Corinna Vinschen
2015-02-09 17:16       ` Achim Gratz [this message]
2015-02-09 18:49         ` perl-5.14.4 Corinna Vinschen
2015-02-09 19:06           ` perl-5.14.4 Corinna Vinschen
2015-02-09 19:41           ` perl-5.14.4 Achim Gratz
2015-02-09 20:20             ` perl-5.14.4 Corinna Vinschen
2015-02-14 20:04     ` perl-5.14.4 Achim Gratz
2015-02-14 21:12       ` perl-5.14.4 Achim Gratz
2015-02-15 10:32         ` perl-5.14.4 Corinna Vinschen
2015-02-15 13:18           ` perl-5.14.4 Achim Gratz
2015-02-15 14:31             ` perl-5.14.4 Corinna Vinschen
2015-02-15 16:22               ` perl-5.14.4 Achim Gratz
2015-02-15 19:14               ` perl-5.14.4 Achim Gratz
2015-02-16  9:17                 ` perl-5.14.4 Corinna Vinschen
2015-02-16  9:46                   ` perl-5.14.4 Achim Gratz
2015-02-16 10:25                     ` perl-5.14.4 Corinna Vinschen
2015-02-16 12:25                       ` perl-5.14.4 Corinna Vinschen
2015-02-16 14:29                         ` perl-5.14.4 Achim Gratz
2015-02-16 15:32                           ` perl-5.14.4 Corinna Vinschen
2015-02-16 15:42                             ` perl-5.14.4 Achim Gratz
2015-03-05 13:21                               ` perl-5.14.4 Corinna Vinschen
2015-03-05 16:45                                 ` perl-5.14.4 Achim Gratz
2015-03-10  9:10                                 ` perl-5.14.4 Corinna Vinschen
2015-03-14 20:30                                   ` perl-5.14.4 Achim Gratz
2015-03-16  9:06                                     ` perl-5.14.4 Corinna Vinschen
2015-02-10 19:55 ` perl-5.14.4 Achim Gratz
2015-02-11 20:01 ` perl-5.14.4 David Stacey
2015-02-13 18:36   ` perl-5.14.4 Achim Gratz

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=87vbjbuhtf.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=cygwin-apps@cygwin.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).