diff options
fix leak when getline fails
according to the getline(3) documentation, the calling code needs to
free the buffer even if getline fails.
dmenu currently doesn't do that which results in a small leak in case of
failure (e.g when piped /dev/null)
$ ./dmenu < /dev/null
==8201==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 120 byte(s) in 1 object(s) allocated from:
#0 0x7f6bf5785ef7 in malloc
#1 0x7f6bf538ec84 in __getdelim
#2 0x405d0c in readstdin dmenu.c:557
moving `line = NULL` inside the loop body wasn't strictly necessary, but
IMO it makes it more apparent that `line` is getting cleared to NULL
after each successful iteration.
Diffstat (limited to '%2525252525253fid%2525252525253ddfbbf7f6e1b22ccf9e5a45d77ee10995577fb4fc%25252525253fid%25252525253dba1a347dcaba055f824161007dfee60db3ea785b%252525253fid%252525253dba1a347dcaba055f824161007dfee60db3ea785b%2525253fid%2525253dba1a347dcaba055f824161007dfee60db3ea785b&id2%2525253dbcbc1ef5c4cf4875a4d66e7dc0919da88a6096a5%25253fid%25253dba1a347dcaba055f824161007dfee60db3ea785b%253fid%253dbcbc1ef5c4cf4875a4d66e7dc0919da88a6096a5%3fid%3dbcbc1ef5c4cf4875a4d66e7dc0919da88a6096a5?id=689d9bfcf6859e5ce85c296ff0f23b5c08b1fedc')
0 files changed, 0 insertions, 0 deletions