Backtrace symbol address to file and line mappings
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 14.4k
- Forks
- 1.3k
- PR merge metrics
- No merged PRs in 30d
Description
The current implementation of exceptions uses GCCBacktrace to gather the source locations of functions in the backtrace. It's not portable or widely available, even on Linux.
The fallback code, if libbacktrace is not available, does just print symbol names, but not their source file origin.
Therefore it would be good to have a cross-platform backtrace library such as Boost.Backtrace. Another option is libdwarf, but that is only available for Linux ELF.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the current GCCBacktrace implementation and its libbacktrace fallback, then review how Boost.Backtrace and libdwarf could provide source file and line mappings. Done means backtraces report file and line origins through a portable approach rather than only symbol names.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100