Hello,
what's the status of the fix/patch in this bug?
We see many leaks for cryptsetup in valgrind tests if running under Debian
(while other distros apparently do not have this problem) and it seems
all reported problems are with poptGetNextOpt ...
Thanks,
Milan
First look:
Seems like gdisk uses a popt internal argv string after
poptResetContext() [1] and svox frees one [2].
[1] https://sources.debian.org/src/gdisk/1.0.4-3/gptcl.cc/?hl=153#L158
Line 152: get leftover string
Line 153: call popResetContext(), which free's with the patch
Line 158: use this
found #941814
Regressions were reported in gdisk and svox, I reverted the patch until
more testing can be done.
gdisk/1.0.4-3:
https://ci.debian.net/data/autopkgtest/testing/amd64/g/gdisk/3216686/log.gz
svox/1.0+git20130326-9:
https://ci.debian.net/data/autopkgtest/testing/amd64/s/svox/3216687
Package: libpopt0
Version: 1.16-12
Severity: important
Affects: logrotate
Tags: patch
The patch 318833-incorrect-handling-of-leftovers-with-poptStuffArgs.patch
introduces a memory leak for leftover arguments.
Previously the content of 'con->leftovers' did not hold own memory, so
it did not need t
4 matches
Mail list logo
