From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: [RFC] cygport: split debuginfo packages
Date: Sun, 01 Mar 2015 19:25:00 -0000 [thread overview]
Message-ID: <1425237937.9892.10.camel@cygwin.com> (raw)
In-Reply-To: <54F35239.6060002@dronecode.org.uk>
On Sun, 2015-03-01 at 17:54 +0000, Jon TURNEY wrote:
> On 27/02/2015 06:27, Yaakov Selkowitz wrote:
> > On Mon, 2015-02-23 at 12:14 +0000, Jon TURNEY wrote:
> >> On 07/07/2012 14:10, Jon TURNEY wrote:
> >>> I was going to suggest the use of objcopy --compress-debug-sections, but it
> >>> appears that does nothing for PE/COFF files at the moment [1] :-(
> >>>
> >>> [1] http://sourceware.org/bugzilla/show_bug.cgi?id=14067
> >>
> >> That bug has been fixed for a while, so how about the attached?
> >>
> >> This appears to reduce the disk space used by .dbg files to about 1/3 of
> >> the size, so seems worthwhile.
> >
> > Have you tested that the resulting split debuginfo work properly with
> > gdb?
>
> It's hardly a comprehensive test, but I did try this:
[snip]
Fair enough, I have pulled in this patch for further testing.
Thanks,
Yaakov
next prev parent reply other threads:[~2015-03-01 19:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-21 6:24 Yaakov (Cygwin/X)
2012-06-21 9:03 ` Corinna Vinschen
2012-06-21 9:35 ` Corinna Vinschen
2012-06-21 19:47 ` Yaakov (Cygwin/X)
2012-06-22 9:51 ` Corinna Vinschen
2012-06-21 12:56 ` Christopher Faylor
2012-06-21 14:22 ` Jon TURNEY
2012-06-21 16:10 ` Christopher Faylor
2012-06-22 15:23 ` Ken Brown
2012-06-29 19:48 ` Yaakov (Cygwin/X)
2012-06-30 16:49 ` Ken Brown
2012-07-07 13:11 ` Jon TURNEY
2015-02-23 12:15 ` Jon TURNEY
2015-02-27 6:27 ` Yaakov Selkowitz
2015-03-01 17:54 ` Jon TURNEY
2015-03-01 19:25 ` Yaakov Selkowitz [this message]
2015-03-09 12:55 ` Jon TURNEY
2012-07-17 18:37 ` Achim Gratz
2012-07-17 18:39 ` Christopher Faylor
2012-07-17 19:48 ` Achim Gratz
2012-07-17 19:55 ` Christopher Faylor
2012-07-17 20:25 ` Yaakov (Cygwin/X)
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=1425237937.9892.10.camel@cygwin.com \
--to=yselkowitz@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).