Hello, I am trying to run valgrind on my nginx module. According to the NGINX support my nginx configuration is right, and the problem is in the valgrind. Valgrind output: ==3789== Memcheck, a memory error detector ==3789== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==3789== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info ==3789== Command: /home/ortal/iguazio/development/engine/zeek/build/vendor/nginx/sbin/nginx -p . ==3789== vex: the `impossible' happened: isZeroU vex storage: T total 673465552 bytes allocated vex storage: P total 640 bytes allocated valgrind: the 'impossible' happened: LibVEX called failure_exit(). host stacktrace: ==3789== at 0x38083F48: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==3789== by 0x38084064: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==3789== by 0x380842A1: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==3789== by 0x380842CA: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==3789== by 0x3809F682: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==3789== by 0x38148008: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==3789== by 0x3815514D: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==3789== by 0x38159272: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==3789== by 0x38159EA6: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==3789== by 0x3815BD68: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==3789== by 0x3815CDB6: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==3789== by 0x38145DEC: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==3789== by 0x380A1C0B: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==3789== by 0x380D296B: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==3789== by 0x380D45CF: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) ==3789== by 0x380E3946: ??? (in /usr/lib/valgrind/memcheck-amd64-linux) sched status: running_tid=1 Thread 1: status = VgTs_Runnable (lwpid 3789) ==3789== at 0x57FB4E0: ??? (in /lib/x86_64-linux-gnu/libcrypto.so.1.0.0) ==3789== by 0x57DA6FF: EC_POINT_mul (in /lib/x86_64-linux-gnu/libcrypto.so.1.0.0) ==3789== by 0x6179B8F: ??? ==3789== by 0x6176AEF: ??? ==3789== by 0x478AD084BB0BECFF: ??? ==3789== by 0x617679F: ??? ==3789== by 0x57E2E47: EC_KEY_check_key (in /lib/x86_64-linux-gnu/libcrypto.so.1.0.0) ==3789== by 0x57E3260: EC_KEY_set_public_key_affine_coordinates (in /lib/x86_64-linux-gnu/libcrypto.so.1.0.0) ==3789== by 0x589C882: ??? (in /lib/x86_64-linux-gnu/libcrypto.so.1.0.0) ==3789== by 0x589837F: ??? (in /lib/x86_64-linux-gnu/libcrypto.so.1.0.0) ==3789== by 0x5897A33: ??? (in /lib/x86_64-linux-gnu/libcrypto.so.1.0.0) ==3789== by 0x576B70C: FIPS_mode_set (in /lib/x86_64-linux-gnu/libcrypto.so.1.0.0) ==3789== by 0x5767F89: OPENSSL_init_library (in /lib/x86_64-linux-gnu/libcrypto.so.1.0.0) ==3789== by 0x40104E9: call_init.part.0 (dl-init.c:72) ==3789== by 0x40105FA: call_init (dl-init.c:30) ==3789== by 0x40105FA: _dl_init (dl-init.c:120) ==3789== by 0x4000CF9: ??? (in /lib/x86_64-linux-gnu/ld-2.23.so) ==3789== by 0x2: ??? ==3789== by 0xFFEFFFC66: ??? ==3789== by 0xFFEFFFCB0: ??? ==3789== by 0xFFEFFFCB3: ??? Note: see also the FAQ in the source distribution. It contains workarounds to several common problems. In particular, if Valgrind aborted or crashed after identifying problems in your program, there's a good chance that fixing those problems will prevent Valgrind aborting or crashing, especially if it happened in m_mallocfree.c. If that doesn't help, please report this bug to: www.valgrind.org In the bug report, send all the above text, the valgrind version, and what OS and version you are using. Thanks.
This looks very similar to bug 356393, that has been fixed in vex r3213. Can you check by trying the svn version ? Thanks
After updating to the SVN version It works!!! Thanks *** This bug has been marked as a duplicate of bug 356393 ***