Skip to content

Maximum number of backtrace frames is not configurable #64194

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.

Sign up for GitHub

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

Jump to bottom
Closed
Aaron1011 opened this issue Sep 5, 2019 · 2 comments
Closed

Maximum number of backtrace frames is not configurable #64194

Aaron1011 opened this issue Sep 5, 2019 · 2 comments
Labels
T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.

Comments

@Aaron1011
Copy link
Member

The standard library currently has a hard-coded limit of 100 frames when printing a backtrace. However, some applications may have larger call stacks - without rebuilding libstd, it's impossible for them to obtain proper backtraces.

The standard library should provide an environment variable which overrides the default backtrace frame limit.
@Aaron1011 Aaron1011 changed the title Maximum number of backtrace frames is too small Maximum number of backtrace frames is not configurable Sep 5, 2019
@cramertj
Copy link
Member

cramertj commented Sep 5, 2019

Once #64152 lands, RUST_BACKTRACE=full will bypass this limit.

@Mark-Simulacrum Mark-Simulacrum added the T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. label Sep 6, 2019
@Aaron1011
Copy link
Member Author

Fixed in #64152

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Aaron1011 @Mark-Simulacrum @cramertj