unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Malte Frank Gerdes <malte.f.gerdes@gmail.com>
To: 44081@debbugs.gnu.org
Subject: bug#44081: qtbase strips debug info from the debug output
Date: Mon, 19 Oct 2020 21:48:49 +0200	[thread overview]
Message-ID: <86blgyatem.fsf@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 951 bytes --]

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.

I tested other packages based on gnu-build-system; there every .debug
file that's in the debug output contains the debug info as
expected. This can be checked with `readelf --debug-dump
<path-to-file>'.

I read the package defintions but can't see where it goes wrong.

Attached is build log of qtbase with (outputs '("out" "debug")) added to
it's package definition. Note that during the strip phase strip issues
warnings regarding files in the debug output which should simply not be
because this (imho) where strip strips the debug info from the .debug
files.

Any help and/or clarification as to what is happening here is much
appreciated :)


Malte


[-- Attachment #2: 28yn4lc656prrqgrjbfx84ixhv07jz-qtbase-5.14.2.drv.bz2 --]
[-- Type: application/octet-stream, Size: 317599 bytes --]

             reply	other threads:[~2020-10-19 19:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-19 19:48 Malte Frank Gerdes [this message]
2020-10-21  2:40 ` bug#44081: qtbase strips debug info from the debug output Maxim Cournoyer
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=86blgyatem.fsf@gmail.com \
    --to=malte.f.gerdes@gmail.com \
    --cc=44081@debbugs.gnu.org \
    /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).