ods-ksmutil update seqfaults when releasing db lock

Have the database in a dir owned by root. Configure the enforcer to drop privs to an user.

Set up the database:
sudo ods-ksmutil setup

You now have three file:
enforcer.db
enforcer.db.backup
enforcer.our_lock

enforcer.db and enforcer.db.our_lock is owned by the user.

Update the database (not using sudo):
ods-ksmutil update

It segfaults. This is the stack trace from gdb:

Error releasing db lock
Program received signal SIGABRT, Aborted.
[Switching to Thread 0xb7a0e6b0 (LWP 4902)]
0xb7ee6410 in __kernel_vsyscall ()
(gdb) bt
#0 0xb7ee6410 in __kernel_vsyscall ()
#1 0xb7a92085 in raise () from /lib/tls/i686/cmov/libc.so.6
#2 0xb7a93a01 in abort () from /lib/tls/i686/cmov/libc.so.6
#3 0xb7acab7c in ?? () from /lib/tls/i686/cmov/libc.so.6
#4 0xb7ad2a85 in ?? () from /lib/tls/i686/cmov/libc.so.6
#5 0xb7ad64f0 in free () from /lib/tls/i686/cmov/libc.so.6
#6 0xb7ac13e4 in fclose () from /lib/tls/i686/cmov/libc.so.6
#7 0x08050162 in cmd_update () at ../../../enforcer/utils/ksmutil.c:575
#8 0x0805383b in main (argc=<value optimized out>, argv=0xbfa59aa8) at ../../../enforcer/utils/ksmutil.c:2297