https://bugs.kde.org/show_bug.cgi?id=461074
Gao Liang <cbs.gaoli...@huawei.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CONFIRMED |REPORTED
Ever confirmed|1 |0
CC| |cbs.gaoli...@huawei.com
--- Comment #9 from Gao Liang <cbs.gaoli...@huawei.com> ---
I also recently encounted this problem when I ran pytorch with valgrind on
arm64 platform.
I tried to make the following changes to coregrind/m_debuginfo/readwarf.c (the
codebase is valgrind-3.21.0) that fixed the blocking problem in my environment,
although I'm not quite sure if it's correct. For Mathieu Malaterre and others:
case DW_OP_breg0 ... DW_OP_breg31:
break;
// === BEGIN support DW_OP_bregx(0x92) ===
case DW_OP_bregx:
uw = (UWord)step_leb128U( &expr );
sw = step_leb128S( &expr );
ix = ML_(CfiExpr_Binop)( dst,
Cbinop_Add,
ML_(CfiExpr_DwReg)( dst, uw ),
ML_(CfiExpr_Const)( dst, (UWord)sw )
);
PUSH(ix);
if (ddump_frames)
VG_(printf)("DW_OP_bregx: %ld", sw);
break;
// === END support DW_OP_bregx(0x92) ===
case DW_OP_reg0 ... DW_OP_reg31:
……
--
You are receiving this mail because:
You are watching all bug changes.
