unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Malte Frank Gerdes <malte.f.gerdes@gmail.com>
Cc: 44081@debbugs.gnu.org
Subject: bug#44081: qtbase strips debug info from the debug output
Date: Tue, 20 Oct 2020 22:40:43 -0400	[thread overview]
Message-ID: <87r1ps47ys.fsf@gmail.com> (raw)
In-Reply-To: <86blgyatem.fsf@gmail.com> (Malte Frank Gerdes's message of "Mon,  19 Oct 2020 21:48:49 +0200")

Hello,

Malte Frank Gerdes <malte.f.gerdes@gmail.com> writes:

> Hi,
>
> i'm trying to get debug symbols for qt related packages. I noticed that
> those inherit from qtsvg which itself inherits from qtbase. The
> behaviour that i see is: before the stripping phase all objects have
> debugging info and afterwards even the separate debug files don't have
> them anymore.

You want to use the staging branch of Guix, as it already includes a
debug output for qtbase and related packages (which inherits from its
definition).

Possibly what was missing from your experiment was the
"--force-debug-info" configure option that prevents the Qt build system
from stripping the debug symbols (the otherwise default behavior).  You
can inspect commit ab6fe9d3620 to see how it was done.

Hope that helps,

Maxim




  reply	other threads:[~2020-10-21  2:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-19 19:48 bug#44081: qtbase strips debug info from the debug output Malte Frank Gerdes
2020-10-21  2:40 ` Maxim Cournoyer [this message]
2020-10-21  3:55   ` Maxim Cournoyer

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r1ps47ys.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=44081@debbugs.gnu.org \
    --cc=malte.f.gerdes@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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