Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Support printing source context out of the box

Open
#50 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp
Domain
devtools

Research direction

The issue names no files, tests, or entry points. Start by locating the library's existing stack-trace printing functionality and review how source locations are represented across supported platforms. Done means printed traces include source-code context automatically, including on Windows, with coverage for the relevant behavior.

Written by the indexing model from the issue text.

Description

enhancement help wanted

I believe currently the biggest "competitor" to Boost.Stacktrace is Backward-cpp. Its main strength is automatic printing of source code context for every frame in the stack trace.

That difference doesn't seem like much at a glance, but it changes the way you develop your programs. You no longer have to manually copy-paste locations from the trace to check what code was in there. Of course the users can automate this functionality themselves, but it would lead to a lot of duplication across projects.

The only downside of Backward-cpp that I noticed so far is lack of support for Windows. Boost.Stacktrace already works there, so if this feature request was implemented, it could improve popularity of this library.

If you are more interested in pushing Boost.Stacktrace as a standard, the proposed feature could also be included in the paper.

Thanks in advance for your consideration.

Dominant language
C++
Stars
497
Forks
86
Avg merge
8d 20h
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from boostorg/stacktrace

All issues in boostorg/stacktrace

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.