From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: [RFC] cygport: split debuginfo packages
Date: Thu, 21 Jun 2012 09:03:00 -0000 [thread overview]
Message-ID: <20120621090309.GA7160@calimero.vinschen.de> (raw)
In-Reply-To: <4FE2BE24.4050508@users.sourceforge.net>
On Jun 21 01:24, Yaakov (Cygwin/X) wrote:
> Attached is a first draft of a patch to support split debuginfo
> packages automatically in cygport. I'm looking for comments and
> suggestions, particularly on the following:
>
> 1) I propose adding a Debug category for all -debuginfo packages.
>
> 2) This places the debuginfo from e.g. /usr/bin/cygfoo-X.dll into
> /usr/lib/debug/usr/bin/cygfoo-X.dbg. Unfortunately, when gdb finds
> library dependencies, they show up as e.g.
> /cygdrive/c/cygwin/bin/cygfoo-X.dll instead of as in /usr/bin,
> causing gdb to not find the debug file. There are at least three
> solutions to this:
>
> a. Fix (cygwin or) gdb to use /usr paths over /cygdrive/c/cygwin paths;
I just had a quick look into this issue and it turns out that GDB
doesn't use cygwin_conv_path in all circumstances. Rather, it uses
realpath in most circumstances.
The problem is a long standing behaviour (since 2005) of realpath:
A DOS path is always converted to its /cygdrive equivalent.
I think the right thing to do here is to fix realpath. It just has
to be done carefully so as not to re-introduce the bugs fixed by
introducing this behaviour back then.
> b. Move debug files to a .debug subdirectory (e.g.
> /usr/bin/.debug/cygfoo-X.dbg);
> c. Move debug files alongside binaries (e.g. /usr/bin/cygfoo-X.dbg).
The upside of c is that debug files alongside the binaries always works.
The downside is the enormous clutter in /bin. I'll fix realpath in the
first place and then we can see how /usr/lib/debug works out, I guess.
> 3) Sources referenced by the .dbg files are placed under
> /usr/src/debug/${PF}, as indicated by the -fdebug-prefix-map flags.
I don't quite understand that. The sources are not part of the
debuginfo package. And usually you'd want to reference the sources
from your builds. Wouldn't /usr/src/${PVR}/src make more sense?
> Unfortunately, this breaks in-tree debugging (e.g. a noinst test or
> sample application). AFAICS, binutils doesn't support changing the
> debug-prefix-map after the fact. Does anyone have any suggestions
> on how to handle this?
Well, there's the "dir" command on the GDB command line...
> 4) The resulting binaries are somewhat larger, having only been
> --strip-debug'ed; what more is lost by --strip-unneeded or
> --strip-all to justify the larger binaries?
I don't know. Did you look with objdump -h what the difference is?
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
next prev parent reply other threads:[~2012-06-21 9:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-21 6:24 Yaakov (Cygwin/X)
2012-06-21 9:03 ` Corinna Vinschen [this message]
2012-06-21 9:35 ` Corinna Vinschen
2012-06-21 19:47 ` Yaakov (Cygwin/X)
2012-06-22 9:51 ` Corinna Vinschen
2012-06-21 12:56 ` Christopher Faylor
2012-06-21 14:22 ` Jon TURNEY
2012-06-21 16:10 ` Christopher Faylor
2012-06-22 15:23 ` Ken Brown
2012-06-29 19:48 ` Yaakov (Cygwin/X)
2012-06-30 16:49 ` Ken Brown
2012-07-07 13:11 ` Jon TURNEY
2015-02-23 12:15 ` Jon TURNEY
2015-02-27 6:27 ` Yaakov Selkowitz
2015-03-01 17:54 ` Jon TURNEY
2015-03-01 19:25 ` Yaakov Selkowitz
2015-03-09 12:55 ` Jon TURNEY
2012-07-17 18:37 ` Achim Gratz
2012-07-17 18:39 ` Christopher Faylor
2012-07-17 19:48 ` Achim Gratz
2012-07-17 19:55 ` Christopher Faylor
2012-07-17 20:25 ` Yaakov (Cygwin/X)
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=20120621090309.GA7160@calimero.vinschen.de \
--to=corinna-cygwin@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).