https://bugs.kde.org/show_bug.cgi?id=486408
Bug ID: 486408
Summary: I have installed Taintgrind using Docker according
https://github.com/wmkhoo/taintgrind?tab=readme-ov-fil
e . I run taintgrind by doing ~/taintgrind$ sudo
docker run -it --rm -v $(pwd):/pwd taintgrind
tests/sign32 . And, it fails.
Classification: Developer tools
Product: valgrind
Version: 3.21.0
Platform: Ubuntu
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: vex
Assignee: jsew...@acm.org
Reporter: liangjenni...@gmail.com
Target Milestone: ---
/code/valgrind/build/bin/valgrind --tool=taintgrind tests/sign32
==9== Taintgrind, the taint analysis tool
==9== Copyright (C) 2010-2018, and GNU GPL'd, by Wei Ming Khoo.
==9== Using Valgrind-3.21.0 and LibVEX; rerun with -h for copyright info
==9== Command: tests/sign32
==9==
1Uto32(t64)
vex: the `impossible' happened:
iselIntExpr_R: cannot reduce tree
vex storage: T total 0 bytes allocated
vex storage: P total 0 bytes allocated
valgrind: the 'impossible' happened:
LibVEX called failure_exit().
host stacktrace:
==9== at 0x58037924: show_sched_status_wrk (m_libcassert.c:406)
==9== by 0x58037A53: report_and_quit (m_libcassert.c:477)
==9== by 0x58037C8B: vgPlain_core_panic_at (m_libcassert.c:553)
==9== by 0x58037CAF: vgPlain_core_panic (m_libcassert.c:563)
==9== by 0x580CD657: failure_exit (m_translate.c:761)
==9== by 0x581454A7: vpanic (main_util.c:253)
==9== by 0x581B1C2F: iselIntExpr_R_wrk (host_arm64_isel.c:2319)
==9== by 0x581B37C3: iselIntExpr_R (host_arm64_isel.c:1641)
==9== by 0x581B29BF: iselIntExpr_R_wrk (host_arm64_isel.c:1993)
==9== by 0x581B37C3: iselIntExpr_R (host_arm64_isel.c:1641)
==9== by 0x581B3FA7: doHelperCall.isra.29.constprop.30
(host_arm64_isel.c:688)
==9== by 0x581BA217: iselSB_ARM64 (host_arm64_isel.c:4192)
==9== by 0x58141B7F: LibVEX_Translate (main_main.c:1099)
==9== by 0x580D0297: vgPlain_translate (m_translate.c:1831)
==9== by 0x580A267B: vgPlain_scheduler (scheduler.c:1136)
==9== by 0x580F5393: run_a_thread_NORETURN (syswrap-linux.c:102)
==9== by 0xFFFFFFFFFFFFFFFF: ???
sched status:
running_tid=1
Thread 1: status = VgTs_Runnable (lwpid 9)
==9== at 0x40011C0: ??? (in /lib/aarch64-linux-gnu/ld-2.27.so)
client stack range: [0x1FFF000000 0x1FFF000FFF] client SP: 0x1FFF000CE0
valgrind stack range: [0x100289C000 0x100299BFFF] top usage: 5904 of 1048576
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 are receiving this mail because:
You are watching all bug changes.
