Did you try to run the amd process under valgrind and wait until it
crashed? valgrind is very good at reporting segfaults. It would be
even better if you build the binary with debug symlinks, to get
function names instead of addresses from the backtrace.
Changing the init.d script like this would run the amd program under
valgrind and lot any issues into /tmp/amd-log*.
diff -ur ../am-utils-6.1.5/debian/am-utils.init
../am-utils-6.1.5-pere/debian/am-utils.init
--- ../am-utils-6.1.5/debian/am-utils.init 2009-09-14 10:10:50.000000000
+0200
+++ ../am-utils-6.1.5-pere/debian/am-utils.init 2009-09-14 10:27:46.000000000
+0200
@@ -113,7 +113,7 @@
get_amd_args
echo -n "Starting automounter: amd"
- /usr/sbin/amd -F /etc/am-utils/amd.conf $dnsdomain $AMDARGS
+ valgrind --log-file=/tmp/amd-log /usr/sbin/amd -F /etc/am-utils/amd.conf
$dnsdomain $AMDARGS
echo "."
}
Happy hacking,
--
Petter Reinholdtsen
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
