[389-devel] (3rd revision) Please Review {516089} add option to ldlct for deref esearch "-e deref=deref:attr"

[yi zhang]

patched code running through valgrind is below:
============================================================
[yi at f11-32x bin]$ valgrind --num-callers=32 --tool=memcheck 
--leak-check=full --leak-resolution=high ./ldclt-bin -h 
mv64a-vm.idm.lab.bos.redhat.com -p 10368 -D "cn=directory manager" -w 
Secret123 -E 1000 -e esearch -e deref=secretary:uid -e random -b 
ou=people,dc=example,dc=com -f uid=ref.XXX -r 1 -R 999 -n 10 -N 100 -T 
1000 -W 1
==32029== Memcheck, a memory error detector.
==32029== Copyright (C) 2002-2008, and GNU GPL'd, by Julian Seward et al.
==32029== Using LibVEX rev 1884, a library for dynamic binary translation.
==32029== Copyright (C) 2004-2008, and GNU GPL'd, by OpenWorks LLP.
==32029== Using valgrind-3.4.1, a dynamic binary instrumentation framework.
==32029== Copyright (C) 2000-2008, and GNU GPL'd, by Julian Seward et al.
==32029== For more details, rerun with: -v
==32029==
ldclt version 4.23
ldclt[32029]: Starting at Mon Nov  9 16:00:21 2009

ldclt[32029]: Average rate:    8.00/thr  (   8.00/sec), total:     80
ldclt[32029]: Average rate:    9.00/thr  (   9.00/sec), total:     90
ldclt[32029]: Average rate:    9.00/thr  (   9.00/sec), total:     90
ldclt[32029]: Average rate:    9.00/thr  (   9.00/sec), total:     90
ldclt[32029]: Average rate:   10.00/thr  (  10.00/sec), total:    100
ldclt[32029]: Average rate:    8.90/thr  (   8.90/sec), total:     89
ldclt[32029]: Average rate:    9.10/thr  (   9.10/sec), total:     91
ldclt[32029]: Average rate:    9.00/thr  (   9.00/sec), total:     90
...
... (similar to above lines)
...
ldclt[32029]: Average rate:    8.90/thr  (   8.90/sec), total:     89
ldclt[32029]: Average rate:    9.00/thr  (   9.00/sec), total:     90
ldclt[32029]: Average rate:    9.10/thr  (   9.10/sec), total:     91
ldclt[32029]: Global average rate:  817.90/thr  (  9.09/sec), total:   8179
ldclt[32029]: Global number times "no activity" reports: never
ldclt[32029]: Global no error occurs during this session.
ldclt[32029]: Average rate:    9.60/thr  (   9.60/sec), total:     96
ldclt[32029]: Average rate:    9.00/thr  (   9.00/sec), total:     90
ldclt[32029]: Average rate:    9.00/thr  (   9.00/sec), total:     90
ldclt[32029]: Number of samples achieved. Bye-bye...
ldclt[32029]: All threads are dead - exit.
ldclt[32029]: Global average rate:  909.80/thr  (  9.10/sec), total:   9098
ldclt[32029]: Global number times "no activity" reports: never
ldclt[32029]: Global no error occurs during this session.
ldclt[32029]: Ending at Mon Nov  9 16:17:01 2009
ldclt[32029]: Exit status 0 - No problem during execution.
==32029==
==32029== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 77 from 1)
==32029== malloc/free: in use at exit: 112,634 bytes in 433 blocks.
==32029== malloc/free: 155,332 allocs, 154,899 frees, 50,418,474 bytes 
allocated.
==32029== For counts of detected errors, rerun with: -v
==32029== searching for pointers to 433 not-freed blocks.
==32029== checked 106,181,236 bytes.
==32029==
==32029== 1,360 bytes in 10 blocks are possibly lost in loss record 48 of 55
==32029==    at 0x4004E5C: calloc (vg_replace_malloc.c:397)
==32029==    by 0x156D2B: _dl_allocate_tls (in /lib/ld-2.10.1.so)
==32029==    by 0x3122C3: pthread_create@@GLIBC_2.1 (in 
/lib/libpthread-2.10.1.so)
==32029==    by 0x805858E: ldclt_thread_create (port.c:319)
==32029==    by 0x8051C97: runThem (ldclt.c:651)
==32029==    by 0x8057137: main (ldclt.c:3260)
==32029==
==32029== LEAK SUMMARY:
==32029==    definitely lost: 0 bytes in 0 blocks.
==32029==      possibly lost: 1,360 bytes in 10 blocks.
==32029==    still reachable: 111,274 bytes in 423 blocks.
==32029==         suppressed: 0 bytes in 0 blocks.
==32029== Reachable blocks (those to which a pointer was found) are not 
shown.
==32029== To see them, rerun with: --leak-check=full --show-reachable=yes
========================================================

On 11/09/2009 03:45 PM, Rich Megginson wrote:
> yi zhang wrote:
>
>
> ack
>
> I would encourage you to run this through valgrind to make sure you 
> catch any memory errors.
>> ------------------------------------------------------------------------
>>
>> -- 
>> 389-devel mailing list
>> 389-devel at redhat.com
>> https://www.redhat.com/mailman/listinfo/fedora-directory-devel
>
>
> --
> 389-devel mailing list
> 389-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-directory-devel
>