public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: cygport: how to install package sources for debugging without recompiling?
Date: Thu, 30 May 2019 17:04:00 -0000	[thread overview]
Message-ID: <77c7c864-aacd-ec4a-c3a8-7435c2a56a4c@SystematicSw.ab.ca> (raw)
In-Reply-To: <0F7D3B1B3C4B894D824F5B822E3E5A178FD758B0@IRSMSX102.ger.corp.intel.com>

On 2019-05-30 10:37, Soegtrop, Michael wrote:
>> Is there some reason why you can't just install that?
> 
> thanks for the hint - I was not aware that the -debuginfo package contains 
> sources - I thought these just contain dwarf files or similar for stripped 
> binaries and sources are in the -src packages.
> 
> Unfortunately for MinGW debuginfo packages exist only for rather few libraries.
> 
> Also I wonder if there exists something like debug info for stripped binaries
> in Cygwin - similar to .pdb files for MSVC. These seem to be not part of the
> debuginfo packages. Does this mean when I want to debug DLLs I anyway need to
> recompile them because the installed DLLs are stripped and there is no other
> way to get DLLs with debug information?

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

Many Cygwin packages have related -debuginfo packages like other distros have
-debug packages:
	$ apt-cyg listall [a-km-zA-Z]*-debuginfo | wc
	   2110    6330   76602

I am surprised at the number of supported mingw64- packages and the scarcity of
related -debuginfo packages:
	$ apt-cyg listall mingw64- | wc
	    786    2358   31654

$ apt-cyg listall mingw*debuginfo
mingw64-i686-binutils-debuginfo 2.29.1.787c9873-1 x86_64
mingw64-i686-gcc-debuginfo 7.4.0-1 x86_64
mingw64-i686-google-breakpad-debuginfo 20171117_git70914b2d-1 noarch
mingw64-i686-hidapi-debuginfo 0.8.0-rc1-1 noarch
mingw64-i686-libsolv-debuginfo 0.6.27-1 noarch
mingw64-i686-pkg-config-debuginfo 1.6.0-1 x86_64
mingw64-i686-qt4-qmake-debuginfo 4.8.7-1 x86_64
mingw64-i686-runtime-debuginfo 6.0.0-1 noarch
mingw64-i686-tcl-debuginfo 8.6.8-1 noarch
mingw64-i686-tk-debuginfo 8.6.8-1 noarch
mingw64-i686-widl-debuginfo 3.0.0-1 x86_64
mingw64-i686-winpthreads-debuginfo 6.0.0-1 noarch
mingw64-i686-zstd-debuginfo 1.4.0-1 noarch
mingw64-x86_64-binutils-debuginfo 2.29.1.787c9873-1 x86_64
mingw64-x86_64-gcc-debuginfo 7.4.0-1 x86_64
mingw64-x86_64-google-breakpad-debuginfo 20171117_git70914b2d-1 noarch
mingw64-x86_64-hidapi-debuginfo 0.8.0-rc1-1 noarch
mingw64-x86_64-libsolv-debuginfo 0.6.27-1 noarch
mingw64-x86_64-pkg-config-debuginfo 1.6.0-1 x86_64
mingw64-x86_64-qt4-qmake-debuginfo 4.8.7-1 x86_64
mingw64-x86_64-runtime-debuginfo 6.0.0-1 noarch
mingw64-x86_64-tcl-debuginfo 8.6.8-1 noarch
mingw64-x86_64-tk-debuginfo 8.6.8-1 noarch
mingw64-x86_64-widl-debuginfo 3.0.0-1 x86_64
mingw64-x86_64-winpthreads-debuginfo 6.0.0-1 noarch
mingw64-x86_64-zstd-debuginfo 1.4.0-1 noarch

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

  reply	other threads:[~2019-05-30 17:04 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 [this message]
2019-05-30 18:01       ` Soegtrop, Michael
2019-05-31 11:09         ` Brian Inglis

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=77c7c864-aacd-ec4a-c3a8-7435c2a56a4c@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).