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

--biabduction-unsafe-malloc doesn't assume that calloc() and realloc() never return null #1799

Open
apaz-cli opened this issue Nov 11, 2023 · 1 comment

Comments

@apaz-cli
Copy link

When projects make the assumption that malloc() never returns null (as is the default on popular operating systems), they typically also make the same assumptions for calloc() and realloc(). Am I blind and I just need to read the docs, or does a solution for this exist?

@Joao-Peterson
Copy link

my question exactly!

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

No branches or pull requests

2 participants