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.

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

Set free data pointer to a known bad value for debugging #279

Closed
Timidger opened this issue Feb 22, 2019 · 1 comment
Closed

Set free data pointer to a known bad value for debugging #279

Timidger opened this issue Feb 22, 2019 · 1 comment
Labels
Ergonomics Unsound

Comments

@Timidger
Copy link
Member

After just debugging a use-after-free I think it's a good idea to set the data pointer used for memory management to a known bad pointer. This will make debugging easier since it's a very obviously bad.

Probably will just use the ever classic 0xDEADBEEF.
@Timidger
Copy link
Member Author

Eh, actually it's already in the logs and then it just obscures what the data was...nah lets not do this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Ergonomics Unsound
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Timidger