From: oreo639 <oreo639@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: Sun, 10 Mar 2024 08:37:48 +0100 [thread overview]
Message-ID: <20240310073748.0BB5829CE4@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: 921 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/issues/49207#issuecomment-1987116052
Comment:
> is the intended behavior?
I can't speak for what the other Void maintainers intend, but afaict it is working as it is written. In this case, you can use substitute-path to fix the locations for the includes.
For source files you can can download the un-patched sources from https://sources.voidlinux.org (this won't include patches and compile-time generated files though, so be aware of that. For example, the header in this instance is a compile-time generated file.)
Ofc you can also use `disas` in gdb to see the assembly.
Arch Linux, for example, uses debugedit to generate a list of source files referenced in the debug symbols to add them to the dbg packages: https://gitlab.archlinux.org/pacman/pacman/-/blob/master/scripts/libmakepkg/tidy/strip.sh.in#L38-53
next prev parent reply other threads:[~2024-03-10 7:37 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 [this message]
2024-03-10 7:50 ` oreo639
2024-03-14 11:48 ` ahesford
2024-03-14 11:48 ` [ISSUE] [CLOSED] " ahesford
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=20240310073748.0BB5829CE4@inbox.vuxu.org \
--to=oreo639@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).