Petter wrote:
As you had problems building a package with debug info in the binary,
I have made one for you. Please install
http://people.skolelinux.no/pere/debian/packages/lenny/insserv_1.12.0-1_i386.deb
and test it using 'valgrind insserv'. Hopefully it can provide the
file and
[Jonny]
1.12.0-1 cannot be built:
Stranger and stranger. It obviously built on the autobuilders. :/
Are abnormalities in my Debian box?
I am starting to suspect it, yes. We have seen issues with tmpfs
triggered by insserv doing operations too quickly. The tmpfs issues
are kernel bugs (Kel
Petter wrote:
I am starting to suspect it, yes. We have seen issues with tmpfs
triggered by insserv doing operations too quickly. The tmpfs issues
are kernel bugs (Kel already reported them to LKML). Do you use tmpfs
file systems for /etc/ and the location where you tried to build
insserv?
[Jonny]
tmpfs is mounted to /tmp. Others are mounted automatically.
$ cat /proc/mounts | grep tmpfs
tmpfs /lib/init/rw tmpfs rw,nosuid,size=1024k,mode=755 0 0
tmpfs /dev tmpfs rw,size=10240k,mode=755 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
tmpfs /tmp tmpfs
Petter wrote:
Could it be an hardware problem with your machine? Perhaps bad
memory? Running memtest86 might expose it if that is the problem.
Since it is an old machine, a problem may be in hardware. The error was not
found although memtest86+ ran.
--
To UNSUBSCRIBE, email to [EMAIL
[Jonny]
Since it is an old machine, a problem may be in hardware. The error
was not found although memtest86+ ran.
As you had problems building a package with debug info in the binary,
I have made one for you. Please install
Package: insserv
Version: 1.12.0-1
Severity: important
update-rc.d-insserv replaced with update-rc.d does not run by segmentation
fault. In 1.11.0-9, it runs correctly.
# update-rc.d.distrib foobar defaults
System startup links for /etc/init.d/foobar already exist.
# update-rc.d-insserv
[Jonny]
update-rc.d-insserv replaced with update-rc.d does not run by segmentation
fault. In 1.11.0-9, it runs correctly.
How strange. It worked during building in the test suite, and that is
a rather extensive test.
Can you try to run it under valgrind, ie. 'valgrind insserv', and see
why
$ valgrind -v --leak-check=full --show-reachable=yes insserv
==554== Memcheck, a memory error detector.
==554== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al.
==554== Using LibVEX rev 1854, a library for dynamic binary translation.
==554== Copyright (C) 2004-2007, and GNU GPL'd,
[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:
10 matches
Mail list logo
