https://bugs.kde.org/show_bug.cgi?id=409646
Bug ID: 409646
Summary: 1Uto32 can be identified
Product: valgrind
Version: 3.15 SVN
Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: vex
Assignee: jsew...@acm.org
Reporter: marekzmyslow...@poczta.onet.pl
Target Milestone: ---
SUMMARY
While running the taintgrind plugin, the following error occurs:
1Uto32(t60)
vex: the `impossible' happened:
iselIntExpr_R: cannot reduce tree
This happens becuse the 1Uto32 case is not found inside host_arm64_isel.c
(missing the case for Iop_1Uto32)
STEPS TO REPRODUCE
1. Install taintgrind according to the instruction
https://github.com/wmkhoo/taintgrind/
2. Run the simple command
3. /work/temp/valgrind/build/bin/valgrind --tool=taintgrind --file-filter=/work
--taint-start=0 --taint-len=1 ls
OBSERVED RESULT
Crash
EXPECTED RESULT
No crash
SOFTWARE/OS VERSIONS
ARMBIAN 5.83 stable Ubuntu 18.04.2 LTS 4.19.38-sunxi64
Linux pine64so 4.19.38-sunxi64 #5.83 SMP Fri May 3 21:02:31 CEST 2019 aarch64
aarch64 aarch64 GNU/Linux
ADDITIONAL INFORMATION
/work/temp/valgrind/build/bin/valgrind --tool=taintgrind --file-filter=/work
--taint-start=0 --taint-len=1 ls
==18427== Taintgrind, the taint analysis tool
==18427== Copyright (C) 2010-2018, and GNU GPL'd, by Wei Ming Khoo.
==18427== Using Valgrind-3.16.0.GIT and LibVEX; rerun with -h for copyright
info
==18427== Command: ls
==18427==
1Uto32(t60)
vex: the `impossible' happened:
iselIntExpr_R: cannot reduce tree
vex storage: T total 12936 bytes allocated
vex storage: P total 0 bytes allocated
valgrind: the 'impossible' happened:
LibVEX called failure_exit().
host stacktrace:
==18427== at 0x5802CE1C: show_sched_status_wrk (m_libcassert.c:386)
==18427== by 0x5802CF4B: report_and_quit (m_libcassert.c:457)
==18427== by 0x5802D183: vgPlain_core_panic_at (m_libcassert.c:533)
==18427== by 0x5802D1A7: vgPlain_core_panic (m_libcassert.c:543)
==18427== by 0x580B30D7: failure_exit (m_translate.c:749)
==18427== by 0x5813025F: vpanic (main_util.c:253)
==18427== by 0x58191F4F: iselIntExpr_R_wrk (host_arm64_isel.c:2082)
==18427== by 0x58193ABB: iselIntExpr_R (host_arm64_isel.c:1458)
==18427== by 0x58192C4B: iselIntExpr_R_wrk (host_arm64_isel.c:1766)
==18427== by 0x58193ABB: iselIntExpr_R (host_arm64_isel.c:1458)
==18427== by 0x58198D53: doHelperCall.isra.28.constprop.29
(host_arm64_isel.c:685)
==18427== by 0x58199FFB: iselSB_ARM64 (host_arm64_isel.c:3761)
==18427== by 0x5812CB2F: LibVEX_Translate (main_main.c:1047)
==18427== by 0x580B5CEF: vgPlain_translate (m_translate.c:1811)
==18427== by 0x58083CBF: handle_chain_me (scheduler.c:1165)
==18427== by 0x58086DB3: vgPlain_scheduler (scheduler.c:1514)
==18427== by 0x580E68AF: run_a_thread_NORETURN (syswrap-linux.c:101)
==18427== by 0xFFFFFFFFFFFFFFFF: ???
sched status:
running_tid=1
--18427-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) -
exiting
--18427-- si_code=1; Faulting address: 0x140; sp: 0x1004b6d300
valgrind: the 'impossible' happened:
Killed by fatal signal
host stacktrace:
==18427== at 0x580880D8: vgPlain_is_in_syscall (syswrap-main.c:1640)
==18427== by 0x5802C9CF: print_thread_state (m_libcassert.c:324)
==18427== by 0x5802CC0F: show_sched_status_wrk (m_libcassert.c:420)
==18427== by 0x5802CF4B: report_and_quit (m_libcassert.c:457)
==18427== by 0x5802D183: vgPlain_core_panic_at (m_libcassert.c:533)
==18427== by 0x5802D1A7: vgPlain_core_panic (m_libcassert.c:543)
==18427== by 0x580B30D7: failure_exit (m_translate.c:749)
==18427== by 0x5813025F: vpanic (main_util.c:253)
==18427== by 0x58191F4F: iselIntExpr_R_wrk (host_arm64_isel.c:2082)
==18427== by 0x58193ABB: iselIntExpr_R (host_arm64_isel.c:1458)
==18427== by 0x58192C4B: iselIntExpr_R_wrk (host_arm64_isel.c:1766)
==18427== by 0x58193ABB: iselIntExpr_R (host_arm64_isel.c:1458)
==18427== by 0x58198D53: doHelperCall.isra.28.constprop.29
(host_arm64_isel.c:685)
==18427== by 0x58199FFB: iselSB_ARM64 (host_arm64_isel.c:3761)
==18427== by 0x5812CB2F: LibVEX_Translate (main_main.c:1047)
==18427== by 0x580B5CEF: vgPlain_translate (m_translate.c:1811)
==18427== by 0x58083CBF: handle_chain_me (scheduler.c:1165)
==18427== by 0x58086DB3: vgPlain_scheduler (scheduler.c:1514)
==18427== by 0x580E68AF: run_a_thread_NORETURN (syswrap-linux.c:101)
==18427== by 0xFFFFFFFFFFFFFFFF: ???
sched status:
running_tid=1
Segmentation fault
--
You are receiving this mail because:
You are watching all bug changes.
