Google meint dass folgendes vor dem dhcpcd Aufruf hilft:
export MALLOC_CHECK_=0
da bei neueren Versionen der glibc ein doppelter Aufruf von free() nicht mehr toleriert wird:
http://www.linuxquestions.org/questions/linux-newbie-8/dhcpd-double-free-or-corruption-732331/ schriebRecent versions of Linux libc (later than 5.4.23) and GNU libc (2.x) include a malloc implementation which is tunable via environment variables. When MALLOC_CHECK_ is set, a special (less efficient) implementation is used which is designed to be tolerant against simple errors, such as double calls of free() with the same argument, or overruns of a single byte (off-by-one bugs). Not all such errors can be protected against, however, and memory leaks can result. If MALLOC_CHECK_ is set to 0, any detected heap corruption is silently ignored and an error message is not generated; if set to 1, the error message is printed on stderr, but the program is not aborted; if set to 2, abort() is called immediately, but the error message is not generated; if set to 3, the error message is printed on stderr and program is aborted. This can be useful because otherwise a crash may happen much later, and the true cause for the problem is then very hard to track down.
Und es gibt schon nen Bugreport:
https://bugs.archlinux.org/task/29200