Attachment 580151 Details for Bug 816175 – log of failing test582

log of failing test582

error.log (text/x-log), 5.93 KB, created by Karsten Hopp on 2012-04-25 12:32:16 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Karsten Hopp

Created: 2012-04-25 12:32:16 UTC

Size: 5.93 KB

patch

obsolete

>test 582...[SFTP upload using multi interface]
>../libtool --mode=execute /usr/bin/valgrind --tool=memcheck --leak-check=yes --num-callers=16 --log-file=log/valgrind582 ./libtest/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: >log/stdout582 2>log/stderr582
>lib582 returned 1, when expecting 0
> exit FAILED
>== Contents of files in the log/ dir after test 582
>=== Start of file file582.txt
> Moooooooooooo
>  upload this
>=== End of file file582.txt
>=== Start of file stderr582
> URL: Sftp://127.0.0.1:3299/builddir/build/BUILD/curl-7.25.0/tests/log/upload582.txt
> Set to upload 27 bytes
> * About to connect() to 127.0.0.1 port 3299 (#0)
> *   Trying 127.0.0.1...
> * connected
> * Connected to 127.0.0.1 (127.0.0.1) port 3299 (#0)
>=== End of file stderr582
>=== Start of file valgrind582
> ==31499== Memcheck, a memory error detector
> ==31499== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
> ==31499== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
> ==31499== 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:
> ==31499== Parent PID: 31498
> ==31499== 
>  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(0xF06D750, 4, 0) ------
>    PUT(1156) = 0xF06D754:I32
>    ------ IMark(0xF06D320, 4, 0) ------
>    PUT(1152) = 0xF06D320: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(0xF06D324, 4, 0) ------
>    PUT(1152) = 0xF06D324: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(0xF06D328, 4, 0) ------
>    PUT(1152) = 0xF06D328: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} 0xF06D32C: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 170450788 bytes allocated
> vex storage: P total 144 bytes allocated
> valgrind: the 'impossible' happened:
>    LibVEX called failure_exit().
> ==31499==    at 0x380509D0: report_and_quit (m_libcassert.c:210)
> ==31499==    by 0x38050BEF: vgPlain_core_panic_at (m_libcassert.c:294)
> ==31499==    by 0x38050C1F: vgPlain_core_panic (m_libcassert.c:304)
> ==31499==    by 0x3806B9BF: failure_exit (m_translate.c:700)
> ==31499==    by 0x380FB623: vpanic (main_util.c:226)
> ==31499==    by 0x38103043: sanityCheckFail (ir_defs.c:2881)
> ==31499==    by 0x381059BB: tcExpr (ir_defs.c:3185)
> ==31499==    by 0x38106A5F: sanityCheckIRSB (ir_defs.c:3288)
> ==31499==    by 0x380F9D57: LibVEX_Translate (main_main.c:561)
> ==31499==    by 0x3806DF57: vgPlain_translate (m_translate.c:1544)
> ==31499==    by 0x3809BC83: vgPlain_scheduler (scheduler.c:901)
> ==31499==    by 0x380AF997: run_a_thread_NORETURN (syswrap-linux.c:98)
> sched status:
>   running_tid=1
> Thread 1: status = VgTs_Runnable
> ==31499==    at 0xF06D750: OPENSSL_cpuid_setup (in /usr/lib/libcrypto.so.1.0.1)
> ==31499==    by 0xF0F44E3: OPENSSL_add_all_algorithms_noconf (in /usr/lib/libcrypto.so.1.0.1)
> ==31499==    by 0xF431FE7: libssh2_init (in /usr/lib/libssh2.so.1.0.1)
> ==31499==    by 0xF4320B7: ??? (in /usr/lib/libssh2.so.1.0.1)
> ==31499==    by 0xF4235F7: libssh2_session_init_ex (in /usr/lib/libssh2.so.1.0.1)
> ==31499==    by 0xFEE92B7: ??? (in /builddir/build/BUILDROOT/curl-7.25.0-2.fc18.ppc/usr/lib/libcurl.so.4.2.0)
> ==31499==    by 0xFEC66C3: ??? (in /builddir/build/BUILDROOT/curl-7.25.0-2.fc18.ppc/usr/lib/libcurl.so.4.2.0)
> ==31499==    by 0xFEC6A47: ??? (in /builddir/build/BUILDROOT/curl-7.25.0-2.fc18.ppc/usr/lib/libcurl.so.4.2.0)
> ==31499==    by 0xFEC6B13: ??? (in /builddir/build/BUILDROOT/curl-7.25.0-2.fc18.ppc/usr/lib/libcurl.so.4.2.0)
> ==31499==    by 0xFED9577: ??? (in /builddir/build/BUILDROOT/curl-7.25.0-2.fc18.ppc/usr/lib/libcurl.so.4.2.0)
> ==31499==    by 0xFEDA197: ??? (in /builddir/build/BUILDROOT/curl-7.25.0-2.fc18.ppc/usr/lib/libcurl.so.4.2.0)
> ==31499==    by 0xFEDA437: curl_multi_socket_action (in /builddir/build/BUILDROOT/curl-7.25.0-2.fc18.ppc/usr/lib/libcurl.so.4.2.0)
> ==31499==    by 0x10000AE7: notifyCurl (lib582.c:205)
> ==31499==    by 0x10001AF7: test (lib582.c:336)
> ==31499==    by 0xFC211D3: generic_start_main.isra.0 (in /usr/lib/libc-2.15.so)
> ==31499==    by 0xFC2138F: (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.
>=== End of file valgrind582

Actions: View

Attachments on bug 816175: 580151