RE: make test crashes in test020-proxycache

["Howard Chu" <hyc@highlandsun.com>]

> -----Original Message-----
> From: owner-openldap-software@OpenLDAP.org
> [mailto:owner-openldap-software@OpenLDAP.org]On Behalf Of Harry Ruter

> So, make test fails as you can see here :
> 
> ---snipp---
> ...
>   >>>>> Starting test020-proxycache ...
> Starting master slapd on TCP/IP port 9011...
> Using ldapsearch to check that master slapd is running...
> Waiting 5 seconds for slapd to start...
> Using ldapadd to populate the master directory...
> Starting proxy cache on TCP/IP port 9012...
> Using ldapsearch to check that proxy slapd is running...
> Waiting 5 seconds for slapd to start...
> Making queries on the proxy cache...
> Query 1: filter:(sn=Jon) attrs: all
> Query 2: filter:(|(cn=*Jon*)(sn=Jon*)) attrs:cn sn title uid
> Query 3: filter:(sn=Smith*) attrs:cn sn title uid
> Query 4: filter:(sn=Doe*) attrs:cn sn title uid
> Query 5: filter:(uid=bjorn) attrs:mail postaladdress 
> telephonenumber cn uid
> Query 6: filter:(mail=*@example.com) cn sn title uid
> Query 7: filter:(mail=*) cn sn title uid
> Query 1 not cacheable
> Query 2 cacheable
> Query 3 cacheable
> Query 4 cacheable
> Query 5 cacheable
> Query 6 cacheable
> Query 7 not cacheable
> Successfully verified cacheability
> Query 8: filter:(|(cn=*Jones)(sn=Jones)) attrs:cn sn title uid
> ./scripts/test020-proxycache: line 193:  2838 Segmentation fault 
> $SLAPD -f $CONF2 -h $URI2 -d $LVL >$LOG2 2>&1
> ldapsearch failed (255)!
> ./scripts/test020-proxycache: kill: (2838) - No such pid
>  >>>>> ./scripts/test020-proxycache failed (exit 255)
> make[2]: *** [bdb-yes] Error 255
> make[2]: Leaving directory `/work/make/openldap-2.2.4/tests'
> make[1]: *** [test] Error 2
> make[1]: Leaving directory `/work/make/openldap-2.2.4/tests'
> make: *** [test] Error 2
> [PTS0] root@486dx66:/work/make/openldap-2.2.4 #
> ---snipp---
> 
> Are this problems known to someone in the list ?

No known problems

> Is there a possibility to start only this test ?
> What debuglevel shall i use to get more informations
> about the cause for the crash ?

Try this from the test directory, use two separate terminal sessions:
sh run -w test020
(at master PID, hit return)

>From the second session, use gdb and attach to slave process
gdb <path/to/slapd> <slave PID>
continue

In the first session, hit return.

When it crashes again, get a backtrace in gdb.

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support