Cygwin's debuginfo package concept
- Date: Fri, 31 May 2019 10:34:36 +0000
- From: "Soegtrop, Michael" <michael.soegtrop@xxxxxxxxx>
- Subject: Cygwin's debuginfo package concept
Dear Cygwin Team,
this is a follow up on the discussion "cygport: how to install package sources for debugging without recompiling".
I am still struggling to understand the concept behind the -debuginfo packages, e.g. mingw64-x86_64-runtime-debuginfo-6.0.0-1.tar. Is it intentional that this package contains only sources and no .debug file created with "objcopy --only-keep-debug"? If so, what is the general concept for debugging in Cygwin? Should installed DLLs be stripped or unstripped? If they are stripped, where should the debug info be? Is the idea that one has to recompile libraries one wants to debug? Is the concept the same for Cygwin and MinGW DLLs?
If this is just a "not yet implemented" thing, I could help to implement it (especially for MinGW).
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Gary Kershaw
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple