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

Do not close IO when RBuffer is freed #14123

Merged
merged 1 commit into from
May 21, 2019
Merged

Conversation

ret2libc
Copy link
Contributor

Fixes #14115

Copy link
Contributor

@thestr4ng3r thestr4ng3r left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@radare
Copy link
Collaborator

radare commented May 21, 2019 via email

@ret2libc
Copy link
Contributor Author

Ok it seems a good point @radare ! Maybe it's better to just avoid the free at all, given it is not the buffer that creates the file it shouldn't be the buffer to close/free it. Nice catch, I will update the PR soon.

@radare
Copy link
Collaborator

radare commented May 21, 2019 via email

Given the RBuffer_io does not open the file itself, it does not make
sense to close it. It's not its responsability to do it.
@ret2libc ret2libc changed the title Add paramater to let user choose if RBuffer needs to close IO Do not close IO when RBuffer is freed May 21, 2019
@radare radare merged commit cef8af4 into radareorg:master May 21, 2019
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.

Calling izz closes the io fd and breaks subsequent calls
3 participants