From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: [RFC] cygport: split debuginfo packages
Date: Thu, 21 Jun 2012 16:10:00 -0000 [thread overview]
Message-ID: <20120621161016.GB9854@ednor.casa.cgf.cx> (raw)
In-Reply-To: <4FE32DFD.2040500@dronecode.org.uk>
On Thu, Jun 21, 2012 at 03:21:49PM +0100, Jon TURNEY wrote:
>On 21/06/2012 13:56, Christopher Faylor wrote:
>> On Thu, Jun 21, 2012 at 01:24:36AM -0500, 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;
>>
>> Why is this necessary? The path to the debuginfo file is supposed to be
>> in the executable. cygwin1.dll doesn't use cygdrive.
>
>The .gnu_debuglink section is supposed to contain a filename, not a pathname.
> It's up to the debugger to work out where the file is.
>
>[1] http://sourceware.org/gdb/onlinedocs/gdb/Separate-Debug-Files.html
Ah, ok. Thanks. You'd think that I would know this since I maintain gdb
and set up cygwin1.dbg.
cgf
next prev parent reply other threads:[~2012-06-21 16:10 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
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 [this message]
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=20120621161016.GB9854@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@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).