https://bugs.kde.org/show_bug.cgi?id=410102
Bug ID: 410102
Summary: Valgrind ir sanity check failure crash
Product: valgrind
Version: 3.13.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
SUMMARY
Valgrind crashes everytime when trying to check c written program on openWRT
arm device.
Libs used in program:
libm.so.1 => /lib/libm.so.1 (0xb6faf000)
libcurl.so.4 => /usr/lib/libcurl.so.4 (0xb6f62000)
libpthread.so.1 => /lib/libpthread.so.1 (0xb6f3f000)
libuci.so => /lib/libuci.so (0xb6f15000)
libcrypto.so.1.0.0 => /usr/lib/libcrypto.so.1.0.0 (0xb6dec000)
libusb-1.0.so.0 => /usr/lib/libusb-1.0.so.0 (0xb6dbe000)
libmosquitto.so.1 => /usr/lib/libmosquitto.so.1 (0xb6da3000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb6d87000)
libc.so.1 => /lib/libc.so.1 (0xb6d22000)
libssl.so.1.0.0 => /usr/lib/libssl.so.1.0.0 (0xb6cd1000)
ld-uClibc.so.1 => /lib/ld-uClibc.so.0 (0xb6fcf000)
libdl.so.1 => /lib/libdl.so.1 (0xb6cbd000)
libubox.so => /lib/libubox.so (0xb6ca4000)
librt.so.1 => /lib/librt.so.1 (0xb6c90000)
libcares.so.2 => /usr/lib/libcares.so.2 (0xb6c74000)
Bug is similar to one reported here:
https://bugs.kde.org/show_bug.cgi?id=357673
Link says problem is fixed but it still occurs on version 3.13
OBSERVED RESULT
==13632== Memcheck, a memory error detector
==13632== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==13632== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info
==13632== Command: rms_mqtt
==13632==
==13632== Invalid read of size 4
==13632== at 0x4005688: ??? (in /lib/ld-uClibc-1.0.14.so)
==13632== Address 0xbded2764 is on thread 1's stack
==13632== 20 bytes below stack pointer
==13632==
IR SANITY CHECK FAILURE
IRSB {
t0:V128 t1:V128 t2:V128 t3: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(0x4937AF0, 4, 0) ------
PUT(64) = 0x4937AF4:I32
PUT(68) = 0x49ECDD8:I32
------ IMark(0x49ECDD8, 4, 0) ------
t0 = GET:V128(128)
t1 = GET:V128(128)
PUT(128) = t2
PUT(68) = 0x49ECDDC:I32
------ IMark(0x49ECDDC, 4, 0) ------
t3 = GET:I32(64)
PUT(68) = t3
PUT(68) = GET:I32(68); exit-Return
}
IN STATEMENT:
PUT(128) = t2
ERROR = IRTemp use before def in IRExpr
vex: the `impossible' happened:
sanityCheckFail: exiting due to bad IR
vex storage: T total 29453720 bytes allocated
vex storage: P total 0 bytes allocated
valgrind: the 'impossible' happened:
LibVEX called failure_exit().
host stacktrace:
==13632== at 0x3804CAA0: ??? (in /usr/lib/valgrind/memcheck-arm-linux)
sched status:
running_tid=1
Thread 1: status = VgTs_Runnable
==13632== at 0x4937AF0: OPENSSL_cpuid_setup (in /usr/lib/libcrypto.so.1.0.0)
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.
EXPECTED RESULT
Valgrind checking for memory leaks and not crashing
SOFTWARE/OS VERSIONS
https://github.com/openwrt/openwrt/tree/openwrt-18.06/package/devel/valgrind
--
You are receiving this mail because:
You are watching all bug changes.
