Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 576300 Details for
Bug 810992
valgrind dies with ERROR = Iex.Binop: arg tys don't match op tys (OPENSSL_ppc64_probe)
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
the relevant part of the log
valgrind-bz810992.log (text/plain), 5.04 KB, created by
Kamil Dudka
on 2012-04-09 20:31:15 UTC
(
hide
)
Description:
the relevant part of the log
Filename:
MIME Type:
Creator:
Kamil Dudka
Created:
2012-04-09 20:31:15 UTC
Size:
5.04 KB
patch
obsolete
> ==35904== Memcheck, a memory error detector > ==35904== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al. > ==35904== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info > ==35904== Command: /builddir/build/BUILD/curl-7.25.0/tests/libtest/.libs/lt-lib582 Sftp://127.0.0.1:3299/builddir/build/BUILD/curl-7.25.0/tests/log/upload582.txt /builddir/build/BUILD/curl-7.25.0/tests/log/file582.txt mockbuild: > ==35904== Parent PID: 35903 > ==35904== > op name: And64 > op type is (I64,I64) -> I64 > arg tys are (I32,I64) > IR SANITY CHECK FAILURE > IRSB { > t0:I32 t1:I32 t2:I32 t3:I32 t4:F64 t5:F64 t6:I32 t7:I64 > t8:I32 t9:I32 t10:I32 t11:I32 t12:I32 t13:I32 t14:I32 t15:I32 > t16:I32 t17:I32 t18:I32 t19:I32 t20:I32 > IR-NoOp > IR-NoOp > IR-NoOp > IR-NoOp > IR-NoOp > IR-NoOp > IR-NoOp > IR-NoOp > IR-NoOp > IR-NoOp > IR-NoOp > IR-NoOp > IR-NoOp > IR-NoOp > IR-NoOp > ------ IMark(0xF09D168, 4, 0) ------ > PUT(1156) = 0xF09D16C:I32 > ------ IMark(0xF09CD50, 4, 0) ------ > PUT(1152) = 0xF09CD50:I32 > t9 = GET:I32(1184) > t8 = And32(t9,0x3:I32) > t5 = GET:F64(144) > t7 = ReinterpF64asI64(t5) > t4 = I64StoF64(Xor32(t8,And32(Shl32(t8,0x1:I8),0x2:I32)),t7) > PUT(144) = t4 > ------ IMark(0xF09CD54, 4, 0) ------ > PUT(1152) = 0xF09CD54:I32 > t10 = GET:I32(0) > t12 = GET:I32(0) > t11 = And64(Mux0X(And8(0x20:I8,0x1F:I8),t10,Or32(Shl32(t10,And8(0x20:I8,0x1F:I8)),Shr32(t10,Sub8(0x20:I8,And8(0x20:I8,0x1F:I8))))),0xFFFFFFFF:I64) > PUT(0) = t11 > ------ IMark(0xF09CD58, 4, 0) ------ > PUT(1152) = 0xF09CD58:I32 > t18 = 0xFFFFFFFF:I32 > t15 = t18 > t19 = 0x1:I32 > t16 = t19 > t14 = And32(t16,t15) > t17 = And32(GET:I32(1156),0xFFFFFFFC:I32) > if (CmpEQ32(t14,0x0:I32)) goto {Boring} 0xF09CD5C:I32 > goto {Return} t17 > } > IN STATEMENT: > t11 = And64(Mux0X(And8(0x20:I8,0x1F:I8),t10,Or32(Shl32(t10,And8(0x20:I8,0x1F:I8)),Shr32(t10,Sub8(0x20:I8,And8(0x20:I8,0x1F:I8))))),0xFFFFFFFF:I64) > ERROR = Iex.Binop: arg tys don't match op tys > ... additional details precede BB printout > vex: the `impossible' happened: > sanityCheckFail: exiting due to bad IR > vex storage: T total 169981960 bytes allocated > vex storage: P total 144 bytes allocated > valgrind: the 'impossible' happened: > LibVEX called failure_exit(). > ==35904== at 0x380509D0: report_and_quit (m_libcassert.c:210) > ==35904== by 0x38050BEF: vgPlain_core_panic_at (m_libcassert.c:294) > ==35904== by 0x38050C1F: vgPlain_core_panic (m_libcassert.c:304) > ==35904== by 0x3806B9BF: failure_exit (m_translate.c:700) > ==35904== by 0x380FB623: vpanic (main_util.c:226) > ==35904== by 0x38103043: sanityCheckFail (ir_defs.c:2881) > ==35904== by 0x381059BB: tcExpr (ir_defs.c:3185) > ==35904== by 0x38106A5F: sanityCheckIRSB (ir_defs.c:3288) > ==35904== by 0x380F9D57: LibVEX_Translate (main_main.c:561) > ==35904== by 0x3806DF57: vgPlain_translate (m_translate.c:1544) > ==35904== by 0x3809BC83: vgPlain_scheduler (scheduler.c:901) > ==35904== by 0x380AF997: run_a_thread_NORETURN (syswrap-linux.c:98) > sched status: > running_tid=1 > Thread 1: status = VgTs_Runnable > ==35904== at 0xF09D168: OPENSSL_cpuid_setup (in /usr/lib/libcrypto.so.1.0.1) > ==35904== by 0xF11E177: OPENSSL_add_all_algorithms_noconf (in /usr/lib/libcrypto.so.1.0.1) > ==35904== by 0xF440447: libssh2_init (in /usr/lib/libssh2.so.1.0.1) > ==35904== by 0xF440507: ??? (in /usr/lib/libssh2.so.1.0.1) > ==35904== by 0xF432853: libssh2_session_init_ex (in /usr/lib/libssh2.so.1.0.1) > ==35904== by 0xFEE92B7: ??? (in /builddir/build/BUILDROOT/curl-7.25.0-1.fc18.ppc/usr/lib/libcurl.so.4.2.0) > ==35904== by 0xFEC66C3: ??? (in /builddir/build/BUILDROOT/curl-7.25.0-1.fc18.ppc/usr/lib/libcurl.so.4.2.0) > ==35904== by 0xFEC6A47: ??? (in /builddir/build/BUILDROOT/curl-7.25.0-1.fc18.ppc/usr/lib/libcurl.so.4.2.0) > ==35904== by 0xFEC6B13: ??? (in /builddir/build/BUILDROOT/curl-7.25.0-1.fc18.ppc/usr/lib/libcurl.so.4.2.0) > ==35904== by 0xFED9577: ??? (in /builddir/build/BUILDROOT/curl-7.25.0-1.fc18.ppc/usr/lib/libcurl.so.4.2.0) > ==35904== by 0xFEDA197: ??? (in /builddir/build/BUILDROOT/curl-7.25.0-1.fc18.ppc/usr/lib/libcurl.so.4.2.0) > ==35904== by 0xFEDA437: curl_multi_socket_action (in /builddir/build/BUILDROOT/curl-7.25.0-1.fc18.ppc/usr/lib/libcurl.so.4.2.0) > ==35904== by 0x10000AE7: notifyCurl (lib582.c:205) > ==35904== by 0x10001AF7: test (lib582.c:336) > ==35904== by 0xFC3122F: generic_start_main.isra.0 (in /usr/lib/libc-2.15.so) > ==35904== by 0xFC313C3: (below main) (in /usr/lib/libc-2.15.so) > 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.
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 810992
:
576295
| 576300