https://bugs.kde.org/show_bug.cgi?id=356393
Bug ID: 356393
Summary: valgrind (vex) crashes because isZeroU happened
Product: valgrind
Version: unspecified
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: vex
Assignee: jsew...@acm.org
Reporter: dar...@gmail.com
vex: the `impossible' happened:
isZeroU
vex storage: T total 983714392 bytes allocated
vex storage: P total 640 bytes allocated
valgrind: the 'impossible' happened:
LibVEX called failure_exit().
host stacktrace:
==16723== at 0x38083FA8: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
==16723== by 0x380840C4: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
==16723== by 0x38084301: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
==16723== by 0x3808432A: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
==16723== by 0x3809F6C2: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
==16723== by 0x38148008: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
==16723== by 0x3815516D: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
==16723== by 0x38159292: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
==16723== by 0x38159EC6: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
==16723== by 0x3815BDD8: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
==16723== by 0x3815CE26: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
==16723== by 0x38145E0C: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
==16723== by 0x380A1C4B: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
==16723== by 0x380D295B: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
==16723== by 0x380D45BF: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
==16723== by 0x380E3936: ??? (in /usr/lib/valgrind/memcheck-amd64-linux)
sched status:
running_tid=1
Thread 1: status = VgTs_Runnable (lwpid 16723)
==16723== at 0x5EA6F40: ecp_nistz256_avx2_select_w7 (in
/usr/lib/libcrypto.so.1.0.0)
==16723== by 0x5E765CF: EC_POINT_mul (in /usr/lib/libcrypto.so.1.0.0)
==16723== by 0x5E75416: EC_POINT_new (in /usr/lib/libcrypto.so.1.0.0)
==16723== by 0x5E7EE89: EC_KEY_generate_key (in /usr/lib/libcrypto.so.1.0.0)
==16723== by 0x5B422A4: ssl3_send_client_key_exchange (in
/usr/lib/libssl.so.1.0.0)
==16723== by 0x5B45F67: ssl3_connect (in /usr/lib/libssl.so.1.0.0)
==16723== by 0x5B50E9B: ssl23_connect (in /usr/lib/libssl.so.1.0.0)
==16723== by 0x452B2F: ssl_connect_with_timeout_callback (openssl.c:506)
==16723== by 0x44DDF3: run_with_timeout (utils.c:2046)
==16723== by 0x4529A9: ssl_connect_wget (openssl.c:559)
==16723== by 0x429A0F: establish_connection (http.c:2144)
==16723== by 0x425BAE: gethttp (http.c:3055)
==16723== by 0x4243C5: http_loop (http.c:3971)
==16723== by 0x43FE0E: retrieve_url (retr.c:817)
==16723== by 0x4365C2: main (main.c:1868)
Valgrind crashed with the following message when trying to test GNU Wget. The
issue is triggered only by two specific tests that require Wget to connect to a
proxy server over HTTPS. It does not happen during normal connections to HTTPS
servers. Also, the issue occurs only when compiled with OpenSSL. With GnuTLS
there are no problems.
P.S.: I'm using Valgrind 3.11 on Arch Linux. The version option is not
available in the form. The issue seems to be a regression since it doesn't come
up on an older version (3.7.0) during the CI builds on Travis.
Reproducible: Always
Steps to Reproduce:
1. git clone http://git.savannah.gnu.org/r/wget.git
2. cd wget
3. ./bootstrap && ./configure --enable-valgrind-tests --with-ssl=openssl
4. make check
Actual Results:
The output present above
--
You are receiving this mail because:
You are watching all bug changes.
