void-linux / void-linux/void-packages
64bit Valgrind fails to trace 32bit applications
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 3.4k
- Forks
- 2.8k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 299
Description
Is this a new report?
Yes
System Info
Void 6.12.19_1 x86_64 AuthenticAMD uptodate rrrrmmnFFFFFFFF
Package(s) Affected
valgrind-3.24.0_1, valgrind-32bit-3.16.1_1
Does a report exist for this bug with the project's home (upstream) and/or another distro?
No response
Expected behaviour
launching valgrind wine32 should produce more-or-less the same output as valgrind wine64:
==6727== Memcheck, a memory error detector ==6727== Copyright (C) 2002-2024, and GNU GPL'd, by Julian Seward et al. ==6727== Using Valgrind-3.24.0 and LibVEX; rerun with -h for copyright info ==6727== Command: wine64 ==6727== Usage: wine PROGRAM [ARGUMENTS...] Run the specified program wine --help Display this help and exit wine --version Output version information and exit ==6727== ==6727== HEAP SUMMARY: ==6727== in use at exit: 4,094 bytes in 24 blocks ==6727== total heap usage: 32 allocs, 8 frees, 6,738 bytes allocated ==6727== ==6727== LEAK SUMMARY: ==6727== definitely lost: 116 bytes in 2 blocks ==6727== indirectly lost: 0 bytes in 0 blocks ==6727== possibly lost: 0 bytes in 0 blocks ==6727== still reachable: 3,978 bytes in 22 blocks ==6727== suppressed: 0 bytes in 0 blocks ==6727== Rerun with --leak-check=full to see details of leaked memory ==6727== ==6727== For lists of detected and suppressed errors, rerun with: -s ==6727== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Actual behaviour
running valgrind wine32 only produces one line:
valgrind: failed to start tool 'memcheck' for platform 'x86-linux': No such file or directory
additionaly, running strace valgrind wine32 reveals that it expects memcheck-x86-linux to be at /usr/libexec/valgrind/memcheck-x86-linux, however, xbps-query -f valgrind-32bit shows respective file at /usr/lib/valgrind/memcheck-x86-linux instead.
Steps to reproduce
run valgrind wine32
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare the installed paths reported for valgrind-3.24.0_1 and valgrind-32bit-3.16.1_1, focusing on /usr/libexec/valgrind/memcheck-x86-linux and /usr/lib/valgrind/memcheck-x86-linux. Reproduce with valgrind wine32 and use strace to verify the lookup; done means the 32-bit Memcheck tool is found and starts successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100