Re: diagnosing test failures

[Rick Jones <raj@cup.hp.com>]

I've managed to get a system call trace of slapd that shows the source
of the EBADF error coming from the berkeley db-2.7.7 when test003 is
run:

write(2, "  ) \n", 3) .................................... = 3
open("./test-db/dn2id.dbb", O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE, 0600)
ERR#17 EEXI
ST
fcntl(-1, F_SETFD, 1) .................................... ERR#9 EBADF
close(-1) ................................................ ERR#9 EBADF
read(-1, 0x7f7a3b40, 512) ................................ ERR#9 EBADF
close(-1) ................................................ ERR#9 EBADF
stat64("/var/tmp", 0x7f7a41e0) ........................... = 0

under HP-UX at least if O_CREAT and O_EXCL are set on the open, and the
file already exists, the open will fail with an EEXIST. i'm not sure if
that is the behaviour on other platforms. if it is, then I may need to
try and figure-out if something is just not being cleaned-up correctly
in the middle of the test.

from what I've been able to backtrack through the ldap sources, it will
open the db with O_CREAT and the O_EXCL comes from the db itself (or so
it would seem).

rick jones
-- 
these opinions are mine, all mine; HP might not want them anyway... :)
feel free to email, OR post, but please do NOT do BOTH...
my email address is raj in the cup.hp.com domain...