public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Soegtrop, Michael" <michael.soegtrop@intel.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: cygport: how to install package sources for debugging without recompiling?
Date: Thu, 30 May 2019 09:03:00 -0000	[thread overview]
Message-ID: <0F7D3B1B3C4B894D824F5B822E3E5A178FD75804@IRSMSX102.ger.corp.intel.com> (raw)

Dear Cygwin Team,

Cygwin setup allows downloading sources of libraries, but the resulting sources are not immediately useful for debugging. One gets a compressed tar archive, some patches and the cygport file. I know that I can expand sources and apply patches with

cyport <package.cygport> prep

which gives me what I need for debugging, just not in the right place. E.g. some MinGW runtime file is searched by gdb (without giving any directory commands) at

/usr/src/debug/mingw64-x86_64-runtime-6.0.0-1/crt/ucrtexe.c

But after above procedure it is in:

/usr/src/mingw64-x86_64-runtime-6.0.0-1.src/mingw64-x86_64-runtime-6.0.0-1.noarch/src/mingw-w64/mingw-w64-crt/crt/ucrtexe.c

Now of cause I can make a script and copy everything I need where it belongs. But as far as I know

cyport <package.cygport> all

would put the sources in the /usr/src/debug folder. But I don't want to recompile everything, I just want to put the sources where gdb can find them. Is there some way to tell cyport to do this? If not this would be a great additional feature for cygport (which is a very convenient tool).

Thanks & best regards,

Michael
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
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  9:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-30  9:03 Soegtrop, Michael [this message]
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

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=0F7D3B1B3C4B894D824F5B822E3E5A178FD75804@IRSMSX102.ger.corp.intel.com \
    --to=michael.soegtrop@intel.com \
    --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).