This is a slightly modified version of the original `cpp/uninitialized-local` CodeQL query which focuses only on variables using the cleanup macros. Since this has proven to cause issues in the past, let's panic on every uninitialized variable using any of the cleanup macros (as long as they're written using the __cleanup__ attribute). Some test results from a test I used when writing the query: ``` #define _cleanup_foo_ __attribute__((__cleanup__(foo))) #define _cleanup_(x) __attribute__((__cleanup__(x))) static inline void freep(void *p) { *(void**)p = mfree(*(void**) p); } #define _cleanup_free_ _cleanup_(freep) static inline void foo(char **p) { if (*p) *p = free(*p); } int main(void) { __attribute__((__cleanup__(foo))) char *a; char *b; _cleanup_foo_ char *c; char **d; _cleanup_free_ char *e; int r; r = fun(&e); if (r < 0) return 1; puts(a); puts(b); puts(c); puts(*d); puts(e); return 0; } ``` ``` +| test.c:23:14:23:14 | e | The variable $@ may not be initialized here, but has a cleanup handler. | test.c:20:26:20:26 | e | e | +| test.c:27:10:27:10 | a | The variable $@ may not be initialized here, but has a cleanup handler. | test.c:16:45:16:45 | a | a | +| test.c:29:10:29:10 | c | The variable $@ may not be initialized here, but has a cleanup handler. | test.c:18:25:18:25 | c | c | ```
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list or join our IRC channel.
Stable branches with backported patches are available in the stable repo.