Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Link to demangler source in section on using a debugger #1157

Open
rylev opened this issue Jul 1, 2021 · 2 comments
Open

Link to demangler source in section on using a debugger #1157

rylev opened this issue Jul 1, 2021 · 2 comments
Labels
A-debuggers Area: debuggers (lldb, gdb, WinDbg, etc.) A-debuginfo Area: debuginfo E-hard Difficulty: might require advanced knowledge needs-triage This issue needs triage to classify its nature and status T-compiler Relevant to compiler team

Comments

@rylev
Copy link
Member

rylev commented Jul 1, 2021

The location of the demangler was never linked to in the guide on using a debugger in the compiler.

Originally noted here.

@ehuss
Copy link
Contributor

ehuss commented Jul 14, 2022

The sources are at:

if that's what you are asking for. This is for v0 mangling, which is currently (rust-lang/rust#60705) still not the default (except for rustc itself).

@eddyb
Copy link
Member

eddyb commented Jul 14, 2022

It might be a bit early (well, it's functional but lacks a bunch of newer features), but just in case I lose track of this issue, I did end up making a repo for my C port of rustc-demangle (v0-only for now, and mostly the 2019 code that I had eventually integrated into libiberty which binutils/gdb/perf use - see the README for more details though, hopefully I'll eventually get it to feature parity with rustc-demangle).

While I had originally assumed everyone could use libiberty or copy the demangler code from it, that was very naive of me because of licensing issues, so rui314/mold#371 (comment) prompted me to release this separately (see the History section in the README for how exactly that was done to avoid copyright complications).

Feel free to PM me on Zulip with more questions or whenever any of this becomes relevant.

@jieyouxu jieyouxu added E-hard Difficulty: might require advanced knowledge T-compiler Relevant to compiler team needs-triage This issue needs triage to classify its nature and status A-debuginfo Area: debuginfo A-debuggers Area: debuggers (lldb, gdb, WinDbg, etc.) labels Nov 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-debuggers Area: debuggers (lldb, gdb, WinDbg, etc.) A-debuginfo Area: debuginfo E-hard Difficulty: might require advanced knowledge needs-triage This issue needs triage to classify its nature and status T-compiler Relevant to compiler team
Projects
None yet
Development

No branches or pull requests

4 participants