From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: cygport: how to install package sources for debugging without recompiling?
Date: Fri, 31 May 2019 11:09:00 -0000 [thread overview]
Message-ID: <28d91ab5-dec0-6945-3474-c57b77c3a712@SystematicSw.ab.ca> (raw)
In-Reply-To: <0F7D3B1B3C4B894D824F5B822E3E5A178FD75933@IRSMSX102.ger.corp.intel.com>
On 2019-05-30 12:00, Soegtrop, Michael wrote:
>> For Cygwin dlls, look at your installed lib... packages and install the related lib...-
>> debuginfo packages where available:
>> $ apt-cyg listall lib*-debuginfo | wc
>> 350 1050 12704
> As far as I can tell these files only contain sources, but nothing which
> would add debug info to stripped dlls:
> $ tar -xavf mingw64-x86_64-runtime-debuginfo-6.0.0-1.tar.xz
> $ find . -type f | sed -e 's/.*\.//' | sort -u
> c
> h
> s
> xz
>> I am surprised at the number of supported mingw64- packages and the
>> scarcity of related -debuginfo packages:
> the MinGW support in Cygwin has very substantially improved in the last
> years, but indeed many -debuginfo packages for MinGW libs are missing.
The stripped exe debug info is saved as part of each cygport build and supplied
as part of the binary -debuginfo package, if available, under
/usr/lib/debug/usr/.../*.exe.dbg.
With recent cygport releases I believe everything is taken care of unless you
override (or mess up, or don't use) the cygport build and upload defaults.
If I want to try a package, I grab the sources from upstream, copy and modify a
cygport file to do the build, as it makes it so easy to use a variety of tool
chains I am unfamiliar with, and gdb if required for diagnosis.
$ apt-cyg listfiles cygwin-debuginfo | fgrep .dbg
usr/lib/debug/usr/bin/cygwin1.dbg
usr/lib/debug/usr/bin/chattr.exe.dbg
usr/lib/debug/usr/bin/cygpath.exe.dbg
...
usr/lib/debug/usr/bin/cygwin-console-helper.exe.dbg
usr/lib/debug/usr/bin/ldh.exe.dbg
usr/lib/debug/usr/bin/strace.exe.dbg
usr/lib/debug/usr/sbin/cygserver.exe.dbg
$ apt-cyg listfiles coreutils-debuginfo | fgrep .dbg
usr/lib/debug/usr/bin/arch.exe.dbg
usr/lib/debug/usr/bin/b2sum.exe.dbg
usr/lib/debug/usr/bin/base32.exe.dbg
...
usr/lib/debug/usr/bin/whoami.exe.dbg
usr/lib/debug/usr/bin/yes.exe.dbg
usr/lib/debug/usr/bin/[.exe.dbg
usr/lib/debug/usr/libexec/coreutils/libstdbuf.so.dbg
$
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2019-05-31 11:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 9:03 Soegtrop, Michael
2019-05-30 12:52 ` Jon Turney
2019-05-30 14:07 ` Brian Inglis
2019-05-30 16:37 ` Soegtrop, Michael
2019-05-30 17:04 ` Brian Inglis
2019-05-30 18:01 ` Soegtrop, Michael
2019-05-31 11:09 ` Brian Inglis [this message]
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=28d91ab5-dec0-6945-3474-c57b77c3a712@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@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).