From: meator <meator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: gdb can't step in libstdc++
Date: Sun, 10 Mar 2024 07:55:23 +0100 [thread overview]
Message-ID: <20240310065524.003EF2B59C@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: 716 bytes --]
New comment by meator on void-packages repository
https://github.com/void-linux/void-packages/issues/49207#issuecomment-1987110066
Comment:
So
```
std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string (this=0x7fffffffe590)
at ./build/x86_64-unknown-linux-gnu/libstdc++-v3/include/bits/basic_string.h:512
warning: 512 ./build/x86_64-unknown-linux-gnu/libstdc++-v3/include/bits/basic_string.h: No such file or directory
```
is the intended behavior?
My issue might not have been worded exactly. You are correct, gdb can step into whatever it wants to, but here it can't display the code. The warning, especially for a file that is on my system, concerned me.
next prev parent reply other threads:[~2024-03-10 6:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-09 20:32 [ISSUE] " 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 [this message]
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
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=20240310065524.003EF2B59C@inbox.vuxu.org \
--to=meator@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).