[Jonny] > $ valgrind -v --leak-check=full --show-reachable=yes insserv Thank you.
> ==554== Invalid read of size 1 > ==554== at 0x402377E: strcmp (mc_replace_strmem.c:337) > ==554== by 0x80513BA: (within /sbin/insserv) > ==554== by 0x804D5FE: (within /sbin/insserv) > ==554== by 0x4046454: (below main) (in /lib/i686/cmov/libc-2.7.so) > ==554== Address 0x0 is not stack'd, malloc'd or (recently) free'd strcmp() on a NULL pointer, it seem. Can you try again after building a non-stripped version of insserv, ie for example as root: apt-get build-dep insserv DEB_BUILD_OPTIONS=nostrip apt-get source -b insserv dpkg -i insserv*.deb There are a lot of calls to strcmp() in insserv, and without knowing which call got the NULL pointer argument, it is hard to know where to look for the bug. Do you have any idea how I can reproduce this issue? I suspect your content of /etc/init.d/ somehow trigger it. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
