From: David Stacey <drstacey@tiscali.co.uk>
To: cygwin-apps@cygwin.com
Subject: Re: [RFC] Minimal Debuginfo by default
Date: Wed, 15 Nov 2017 09:09:00 -0000 [thread overview]
Message-ID: <7ed5119d-0c11-70a0-9b96-11449d528824@tiscali.co.uk> (raw)
In-Reply-To: <c4e9140a-5993-ecb8-db72-9ca677932c9f@cygwin.com>
On 15/11/17 07:38, Yaakov Selkowitz wrote:
> The following concept would allow for sensible backtraces without
> installing a -debuginfo, at the expense of a moderate size increase of
> binaries (particularly with C++ code):
>
> https://fedoraproject.org/wiki/Changes/MingwMiniDebugInfo
Did you mean https://fedoraproject.org/wiki/Features/MiniDebugInfo
Presumably you intend this for Cygwin binaries.
> The patch for cygport would be minimal. Is it worth the size increase?
The benefit to Fedora is obvious, in that it would increase the quality
of the automated bug reports. Do we have an equivalent in Cygwin (or is
one planned)? Right now, we don't have so many backtraces sent in to the
main list, but who knows - if they were easier to generate then we might.
How would this work for Cygwin? Would we require all the lib.* packages
to be rebuilt?
Dave.
next prev parent reply other threads:[~2017-11-15 9:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 7:38 Yaakov Selkowitz
2017-11-15 9:09 ` David Stacey [this message]
2017-11-19 21:02 ` Yaakov Selkowitz
2017-11-17 14:02 ` Jon Turney
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=7ed5119d-0c11-70a0-9b96-11449d528824@tiscali.co.uk \
--to=drstacey@tiscali.co.uk \
--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).