-
Notifications
You must be signed in to change notification settings - Fork 61
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
malloc question #190
Comments
While pgagroal has a very low memory allocation rate there is def work needed on all error paths - including the one you pointed out. Likely need a fault injection framework like - https://github.com/jesperpedersen/libfaults - to get through them all; including call sites. I welcome contributions to both projects within this space ! |
try use cppcheck -j"$(nproc)" --verbose --force --enable=all --suppress=variableScope . 2> check.err and automate it on test builds |
In this case, do we return only the error code, something like |
Yeah, we should use a |
pgagroal/src/libpgagroal/message.c
Lines 952 to 955 in ce557da
The text was updated successfully, but these errors were encountered: