Github messages for voidlinux
 help / color / mirror / Atom feed
From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: gdb libstdc++ frame gives warning: <line> <file>.h: No such file or directory
Date: Thu, 14 Mar 2024 12:48:54 +0100	[thread overview]
Message-ID: <20240314114854.A527E29DC8@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49207@inbox.vuxu.org>

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

New comment by ahesford on void-packages repository

https://github.com/void-linux/void-packages/issues/49207#issuecomment-1997266231

Comment:
This is definitely not a bug, but an expected consequence of our decision (implicit or otherwise) not to include source in debug packages.

I don't believe shipping source in debug packages is a good idea in general. There are a number of reasons why people might want debug symbols, but in many cases, also having the source sitting around may not be necessary or particularly useful. Having source available for this kinds of things should be an extra opt-in. We don't have a mechanism for that except shipping `-src` packages, which I'm sure nobody wants to do.

If you just need some context for debugging your own stuff, it's easy enough to `./xbps-src -I patch <pkg>` and look through the source. If you're actually trying to debug packaged software, this may be a bit more cumbersome, but there are probably better ways to debug and test packaged software than by trying to use only the packages.

Also note that the generated nature of the header in your example would pose substantial challenges to properly accumulating the source for distribution anyway.

I'm marking this WONTFIX; if any Void member wishes to reopen for more discussion, please do so.

  parent reply	other threads:[~2024-03-14 11:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-09 20:32 [ISSUE] gdb can't step in libstdc++ meator
2024-03-09 20:50 ` meator
2024-03-09 22:33 ` oreo639
2024-03-09 22:44 ` oreo639
2024-03-09 22:44 ` oreo639
2024-03-10  2:04 ` oreo639
2024-03-10  2:05 ` oreo639
2024-03-10  2:21 ` oreo639
2024-03-10  6:49 ` meator
2024-03-10  6:55 ` meator
2024-03-10  7:17 ` oreo639
2024-03-10  7:22 ` oreo639
2024-03-10  7:34 ` gdb libstdc++ frame gives warning: <line> <file>.h: No such file or directory oreo639
2024-03-10  7:37 ` oreo639
2024-03-10  7:50 ` oreo639
2024-03-14 11:48 ` [ISSUE] [CLOSED] " ahesford
2024-03-14 11:48 ` ahesford [this message]
2024-03-14 17:40 ` meator

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=20240314114854.A527E29DC8@inbox.vuxu.org \
    --to=ahesford@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).