I'm putting this here at Lenny's request... Trying to run gfxrecon t

<a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/us

A few notes on this issue: Replay error handling has been upda

linux loader segfault while replaying gfxrecon traces about gfxreconstruct HOT 3 CLOSED

lunarg commented on September 1, 2024

linux loader segfault while replaying gfxrecon traces

from gfxreconstruct.

Comments (3)

KarenGhavam-lunarG commented on September 1, 2024

@lunarpapillo I think this issue should be in the loader project.

from gfxreconstruct.

lunarpapillo commented on September 1, 2024

I think the intent was to first determine whether it was a loader issue or an issue with either the snapshot layer or gfxrecon, before moving it to a different project.

Karen suggested I move it to gfxrecon so Dustin can figure the first part out... but I haven't figured out how to move it yet (without re-entering everything)... Karen, I think you have to have higher permissions than I do to move issues around...

from gfxreconstruct.

dustin-lunarg commented on September 1, 2024

A few notes on this issue:

Replay error handling has been updated such that an API call that succeeded on capture but failed on replay will now cause the tool to print a fatal error and stop playback, instead of printing an error but continuing playback and crashing. This addresses the last case presented in the original issue, running without the screenshot layer, but does not address the loader crash.
If you think that the loader crash is the result of invalid parameters in the capture file, you can enable the validation layers to validate parameters and generate messages for invalid cases.
If you think the loader crash is the result of a loader bug or screenshot layer bug, the issue needs to be reported to either the Vulkan-Loader project or VulkanTools project.

from gfxreconstruct.

Recommend Projects