==1175== Memcheck, a memory error detector.
==1175== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al.
==1175== Using LibVEX rev 1854, a library for dynamic binary translation.
==1175== Copyright (C) 2004-2007, and GNU GPL'd, by OpenWorks LLP.
==1175== Using valgrind-3.3.1-Debian, a dynamic binary instrumentation framework.
==1175== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al.
==1175== For more details, rerun with: -v
==1175== 
==1175== My PID = 1175, parent PID = 453.  Prog and args are:
==1175==    citserver
==1175== 
==1175== Conditional jump or move depends on uninitialised value(s)
==1175==    at 0x4100A77: BN_mod_inverse (in /usr/lib/i686/cmov/libcrypto.so.0.9.8)
==1175==    by 0x4104960: BN_MONT_CTX_set (in /usr/lib/i686/cmov/libcrypto.so.0.9.8)
==1175==    by 0x4104CA7: BN_MONT_CTX_set_locked (in /usr/lib/i686/cmov/libcrypto.so.0.9.8)
==1175==    by 0x4123DE0: (within /usr/lib/i686/cmov/libcrypto.so.0.9.8)
==1175==    by 0x41238F1: DH_generate_key (in /usr/lib/i686/cmov/libcrypto.so.0.9.8)
==1175==    by 0x405CDEA: ssl3_ctx_ctrl (in /usr/lib/i686/cmov/libssl.so.0.9.8)
==1175==    by 0x406E84E: SSL_CTX_ctrl (in /usr/lib/i686/cmov/libssl.so.0.9.8)
==1175==    by 0x807F856: (within /usr/sbin/citserver)
==1175==    by 0x8058CBF: (within /usr/sbin/citserver)
==1175==    by 0x804E7AA: (within /usr/sbin/citserver)
==1175==    by 0x4440454: (below main) (in /lib/libc-2.7.so)
==1175== 
==1175== Conditional jump or move depends on uninitialised value(s)
==1175==    at 0x40F7491: BN_div (in /usr/lib/i686/cmov/libcrypto.so.0.9.8)
==1175==    by 0x40FD5B1: BN_nnmod (in /usr/lib/i686/cmov/libcrypto.so.0.9.8)
==1175==    by 0x410138A: BN_mod_inverse (in /usr/lib/i686/cmov/libcrypto.so.0.9.8)
==1175==    by 0x4104960: BN_MONT_CTX_set (in /usr/lib/i686/cmov/libcrypto.so.0.9.8)
==1175==    by 0x4104CA7: BN_MONT_CTX_set_locked (in /usr/lib/i686/cmov/libcrypto.so.0.9.8)
==1175==    by 0x4123DE0: (within /usr/lib/i686/cmov/libcrypto.so.0.9.8)
==1175==    by 0x41238F1: DH_generate_key (in /usr/lib/i686/cmov/libcrypto.so.0.9.8)
==1175==    by 0x405CDEA: ssl3_ctx_ctrl (in /usr/lib/i686/cmov/libssl.so.0.9.8)
==1175==    by 0x406E84E: SSL_CTX_ctrl (in /usr/lib/i686/cmov/libssl.so.0.9.8)
==1175==    by 0x807F856: (within /usr/sbin/citserver)
==1175==    by 0x8058CBF: (within /usr/sbin/citserver)
==1175==    by 0x804E7AA: (within /usr/sbin/citserver)
==1175== 
==1175== Conditional jump or move depends on uninitialised value(s)
==1175==    at 0x40F7491: BN_div (in /usr/lib/i686/cmov/libcrypto.so.0.9.8)
==1175==    by 0x41049C2: BN_MONT_CTX_set (in /usr/lib/i686/cmov/libcrypto.so.0.9.8)
==1175==    by 0x4104CA7: BN_MONT_CTX_set_locked (in /usr/lib/i686/cmov/libcrypto.so.0.9.8)
==1175==    by 0x4123DE0: (within /usr/lib/i686/cmov/libcrypto.so.0.9.8)
==1175==    by 0x41238F1: DH_generate_key (in /usr/lib/i686/cmov/libcrypto.so.0.9.8)
==1175==    by 0x405CDEA: ssl3_ctx_ctrl (in /usr/lib/i686/cmov/libssl.so.0.9.8)
==1175==    by 0x406E84E: SSL_CTX_ctrl (in /usr/lib/i686/cmov/libssl.so.0.9.8)
==1175==    by 0x807F856: (within /usr/sbin/citserver)
==1175==    by 0x8058CBF: (within /usr/sbin/citserver)
==1175==    by 0x804E7AA: (within /usr/sbin/citserver)
==1175==    by 0x4440454: (below main) (in /lib/libc-2.7.so)
==1175== 
    Valgrind's memory management: out of memory:
       memcheck:allocate new SecMap's request for 16384 bytes failed.
       277454848 bytes have already been allocated.
    Valgrind cannot continue.  Sorry.

    There are several possible reasons for this.
    - You have some kind of memory limit in place.  Look at the
      output of 'ulimit -a'.  Is there a limit on the size of
      virtual memory or address space?
    - You have run out of swap space.
    - Valgrind has a bug.  If you think this is the case or you are
    not sure, please let us know and we'll try to fix it.
    Please note that programs can take substantially more memory than
    normal when running under Valgrind tools, eg. up to twice or
    more, depending on the tool.  On a 64-bit machine, Valgrind
    should be able to make use of up 32GB memory.  On a 32-bit
    machine, Valgrind should be able to use all the memory available
    to a single process, up to 4GB if that's how you have your
    kernel configured.  Most 32-bit Linux setups allow a maximum of
    3GB per process.

    Whatever the reason, Valgrind cannot continue.  Sorry.