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

feature request: api dump pointer tagging #1898

Open
zmike opened this issue Oct 5, 2023 · 1 comment
Open

feature request: api dump pointer tagging #1898

zmike opened this issue Oct 5, 2023 · 1 comment

Comments

@zmike
Copy link

zmike commented Oct 5, 2023

Currently with VK_APIDUMP_NO_ADDR=true all the pointers become static string values. It'd be awesome if there was an option where these strings could remain static but still be tracked. For example, VkCommandBuffer = address for the first-seen cmdbuf would become VkCommandBuffer = cmdbuf1, where all instances of that cmdbuf's address are translated to cmdbuf1 such that across app runs the output is the same. Indexing pointers like this would enable object comparisons across app runs.

@charles-lunarg
Copy link
Contributor

That would be nice, but it comes with complexity. Every single object type would have its own index & map of created objects, and every use would need to access the map to figure out if its an existing handle or a new one. Not a terribly hard problem, but also not 'easy'. Not to mention that this really only works in single threaded applications. Anything with multiple threads means those counters are non deterministic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants