h.b.furuseth@usit.uio.no wrote:

Full_Name: Hallvard B Furuseth Version: HEAD OS: Linux URL: http://folk.uio.no/hbf/OpenLDAP/bug032.tgz Submission from: (NULL) (129.240.202.105) Submitted by: hallvard

Statslog() from even successful tests can show strange sequencing.

grep '^conn=' testrun/slapd.*.log from a test032-chain run shows

• Operations logged on connections before ACCEPT (slapd.1.log conn=2,3 + slapd.2.log conn=7,9)
• Operations on a connection with no ACCEPT (slapd.1.log conn=10), but a 'conn=-1 fd=21 ACCEPT' _after_ that fd's 'close', and valgrind shows memory errors between the close and the ACCEPT.

The enclosed URL gives the testrun directory and test output.

Haven't looked at that yet.

Similar things show up in other tests. A test019 run with a conn=-1 ACCEPT did not get valgrind memory compaints though. grep 'conn=-1' testrun/slapd.*.log also found a number of send_ldap_result: conn=-1 op=0 p=<0 or 3> even in logs without any conn=-1, but maybe that's a "fake connection"? Don't know why results are sent though.

send_ldap_result is always logged, since it occurs before callback processing. So even if it's an internal op with a null callback, it will get logged.