Re: (ITS#5459) threw assertion in attr_dup

[hyc@symas.com]

Aaron Richton wrote:
> Ergh, didn't realize there was more past that.
>
> (dbx)  print a->a_vals[0]
> a->a_vals[0] = {
>       bv_len = 28U
>       bv_val = 0x11925f250 "fixed-address 172.16.143.152"
> }
> (dbx) print a->a_vals[1]
> a->a_vals[1] = {
>       bv_len = 0
>       bv_val = 0x117e9a810 ""
> }
> (dbx) print a->a_vals[2]
> a->a_vals[2] = {
>       bv_len = 0
>       bv_val = (nil)
> }
> (dbx) print a->a_nvals[0]
> a->a_nvals[0] = {
>       bv_len = 28U
>       bv_val = 0x11a48ff90 "fixed-address 172.16.143.152"
> }
> (dbx) print a->a_nvals[1]
> a->a_nvals[1] = {
>       bv_len = 0
>       bv_val = (nil)
> }
>
Is this entry still in your database now? Clearly this condition should never 
happen - if zero-length values are valid for the syntax, then it should have 
been preserved in the (normalized) a_nvals. If not, then it should not have 
been in the a_vals in the first place.

-- 
   -- Howard Chu
   CTO, Symas Corp.           http://www.symas.com
   Director, Highland Sun     http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP  http://www.openldap.org/project/