From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: perl-5.14.4
Date: Tue, 10 Mar 2015 09:10:00 -0000 [thread overview]
Message-ID: <20150310090957.GF5732@calimero.vinschen.de> (raw)
In-Reply-To: <20150305132056.GA3816@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 1633 bytes --]
On Mar 5 14:20, Corinna Vinschen wrote:
> On Feb 16 16:42, Achim Gratz wrote:
> > Corinna Vinschen writes:
> > > Uh oh, the debug information is either broken (which is unlikely) or GDB
> > > doesn't use it anymore due to the CRC mismatch. Maybe the same CRC
> > > mismatch breaks objcopy in cygport, given that both are based on the
> > > same BFD code?
> >
> > Maybe, but none of the tools ever complained about the CRC (I remember
> > that GDB checks it though). A CRC should be a fixable thing, though.
> >
> > > For the time being, is it really required to rebase the DLLs for testing
> > > before the debug information is split off? If you could do the rebase
> > > and test cycle after splitting off the debug info, the problem should be
> > > neglectable.
> >
> > For the moment I've changed the patch to EUMM to check if it's run from
> > cygport and not rebase the just produced DLL in that case. I only need
> > to remember to package the module before testing instead of the other
> > way around (and do a manual rebase before testing, but that isn't
> > difficult). So, I have a workaround.
>
> FYI: https://sourceware.org/bugzilla/show_bug.cgi?id=18025
>
> So the binutils problem is fixed upstream, we're just waiting for GDB
> to catch up. Another collegue of mine will have a look as soon as time
> permits.
Here's one for testing, Achim:
https://cygwin.com/ml/cygwin-announce/2015-03/msg00020.html
Thanks,
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-03-10 9:10 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 ` perl-5.14.4 Achim Gratz
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 ` Corinna Vinschen [this message]
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=20150310090957.GF5732@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).