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

Fix tracing and replaying of Dying Light #906

Closed
wants to merge 2 commits into from

Conversation

speles
Copy link

@speles speles commented Feb 3, 2024

Fixes #493

The fixes are in the recent code, so the issue is probably not the exact same as the original reporter had. But tracing and replaying the Dying Light was broken in 11.1 and current master too.

With these patches, I can confirm that both tracing and replaying actually works.

When the command line of the traced application has no arguments besides
`argv[0]`, the `cmdlineLen - 1` overflows. With sufficiently high `i` it
then eventually causes a buffer overflow and crashes. Fix this by running
this loop only when there are actual arguments.

Signed-off-by: Sviatoslav Peleshko <sviatoslav.peleshko@globallogic.com>
Access like `GL_MAP_WRITE_BIT | GL_MAP_INVALIDATE_BUFFER_BIT` reaches
the default return, while it shouldn't actually be considered coherent.

Signed-off-by: Sviatoslav Peleshko <sviatoslav.peleshko@globallogic.com>
@jrfonseca
Copy link
Member

Hi @speles . Thanks for your contribution. This PR got lost in my inbox somehow -- I only noticed it now. In the meanwhile, both issues were been fixed independently. I sincerely apologize, to you whom fixed these issues first (and accurately!), and the others who ended up replicating your work unnecessarily... I'll try to do better next time.

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

Successfully merging this pull request may close these issues.

Unable to trace Dying Light
2 participants