-
Notifications
You must be signed in to change notification settings - Fork 23
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
process_stats.c:480:4: warning: ignoring return value of ‘fgets’ #91
Comments
Closed
rehsack
added a commit
to rehsack/libstatgrab
that referenced
this issue
Nov 14, 2018
While scanning /proc, when a process disappears, continue scanning instead of working on possible unintialized memory due race condition. Thanks @tdb for reporting (libstatgrab#91) On possible retry failure during fetch all process info via MIB on *BSD, free previously allocated memory on bail out on error. Signed-off-by: Jens Rehsack <sno@netbsd.org>
tdb
pushed a commit
to tdb/libstatgrab
that referenced
this issue
Nov 14, 2018
While scanning /proc, when a process disappears, continue scanning instead of working on possible unintialized memory due race condition. Thanks @tdb for reporting (libstatgrab#91) On possible retry failure during fetch all process info via MIB on *BSD, free previously allocated memory on bail out on error. Signed-off-by: Jens Rehsack <sno@netbsd.org>
tdb
pushed a commit
to tdb/libstatgrab
that referenced
this issue
Nov 14, 2018
While scanning /proc, when a process disappears, continue scanning instead of working on possible unintialized memory due race condition. Thanks @tdb for reporting (libstatgrab#91) On possible retry failure during fetch all process info via MIB on *BSD, free previously allocated memory on bail out on error. Signed-off-by: Jens Rehsack <sno@netbsd.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://github.com/i-scream/libstatgrab/blob/master/src/libstatgrab/process_stats.c#L480
Added in ca9fa77 (unreleased).
The text was updated successfully, but these errors were encountered: