public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/110196] stacktrace_entry does not print which library the function was from Date: Fri, 09 Jun 2023 21:38:48 +0000 [thread overview] Message-ID: <bug-110196-4-eKEHe68kF5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110196-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110196 --- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> --- libbacktrace is supposed to have code to do this, see fileline_initialize in libbacktrace/fileline.c
next prev parent reply other threads:[~2023-06-09 21:38 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-09 15:42 [Bug libstdc++/110196] New: stacktrace_entry does not print origin binary filename fabian_kessler at gmx dot de 2023-06-09 15:56 ` [Bug libstdc++/110196] " pinskia at gcc dot gnu.org 2023-06-09 15:58 ` fabian_kessler at gmx dot de 2023-06-09 16:07 ` fabian_kessler at gmx dot de 2023-06-09 16:09 ` [Bug libstdc++/110196] stacktrace_entry does not print which library the function was from pinskia at gcc dot gnu.org 2023-06-09 16:16 ` fabian_kessler at gmx dot de 2023-06-09 16:17 ` fabian_kessler at gmx dot de 2023-06-09 16:18 ` fabian_kessler at gmx dot de 2023-06-09 16:47 ` fabian_kessler at gmx dot de 2023-06-09 20:56 ` redi at gcc dot gnu.org 2023-06-09 21:38 ` redi at gcc dot gnu.org [this message] 2023-06-10 10:21 ` fabian_kessler at gmx dot de 2023-06-10 12:57 ` fabian_kessler at gmx dot de
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=bug-110196-4-eKEHe68kF5@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).