public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: [RFC] Minimal Debuginfo by default
Date: Sun, 19 Nov 2017 21:02:00 -0000	[thread overview]
Message-ID: <1a6047d6-b8c7-5bf5-cdba-860c2ae4d155@cygwin.com> (raw)
In-Reply-To: <7ed5119d-0c11-70a0-9b96-11449d528824@tiscali.co.uk>


[-- Attachment #1.1: Type: text/plain, Size: 1310 bytes --]

On 2017-11-15 03:09, David Stacey wrote:
> 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.

Yes, but as we're not an ELF platform, I doubt we support the method
used to implement MiniDebugInfo, so the implementation would be closer
to MingwMiniDebugInfo.

>> 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?

Not immediately, but I do think we are getting to the point where we
really need a mass rebuild anyway.  Therefore, I'm trying to queue up
now any changes of such scope.

-- 
Yaakov


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2017-11-19 21:02 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
2017-11-19 21:02   ` Yaakov Selkowitz [this message]
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=1a6047d6-b8c7-5bf5-cdba-860c2ae4d155@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).