KhronosGroup / KhronosGroup/Vulkan-ValidationLayers
option to capture the call stack for each command so it can be shown when an error is detected
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1k
- Forks
- 505
- Avg merge
- 11h 25m
- Merged PRs (30d)
- 229
Description
This was tracked in Projects, converting to an issue:
GPU-AV and sync validation frequently detect errors after the fact, such as at Queue submit time or later. It is often hard to figure out what part of the application code caused the error. Having a saved stack trace for each command would help some developers figure out problems much faster.
Some possible portable implementations:
https://en.cppreference.com/w/cpp/utility/basic_stacktrace (C++23)
https://www.boost.org/doc/libs/1_79_0/doc/html/stacktrace.html
It may be necessary to have a config option pointing to locations of debug symbols.
Contributor guide
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
Start by reviewing the GPU-AV and sync-validation paths that detect errors at Queue submit time or later, then compare the portable C++23 and Boost stacktrace options linked in the issue. Done means commands retain enough call-stack information for the relevant error to show its originating application code, with any debug-symbol configuration addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100