Bug 443426 - Getting valgrind: the 'impossible' happened: Unsupported arch_prctl option when running valgring
Summary: Getting valgrind: the 'impossible' happened: Unsupported arch_prctl option...
Status: RESOLVED DUPLICATE of bug 419562
Alias: None
Product: valgrind
Classification: Developer tools
Component: general (other bugs)
Version First Reported In: 3.15 SVN
Platform: Other Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-10-07 08:19 UTC by Leanna P
Modified: 2021-10-07 08:41 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Leanna P 2021-10-07 08:19:08 UTC
SUMMARY"
When trying to execute valgrind it immediately crashes with valgrind: the 'impossible' happened:
   Unsupported arch_prctl option

This was using WLS with a ubuntu version of 9.1

STEPS TO REPRODUCE
1. Create C executable
2. Enter command "valgrind ./main"

OBSERVED RESULT
==16663== Memcheck, a memory error detector
==16663== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==16663== Using Valgrind-3.14.0.SVN and LibVEX; rerun with -h for copyright info
==16663== Command: ./main
==16663==
==16663== error calling PR_SET_PTRACER, vgdb might block

valgrind: the 'impossible' happened:
   Unsupported arch_prctl option

host stacktrace:
==16663==    at 0x5803D2CA: ??? (in /usr/local/lib/valgrind/memcheck-amd64-linux)
==16663==    by 0x24: ???
==16663==    by 0x1002A9995F: ???
==16663==    by 0x5803D2C9: ??? (in /usr/local/lib/valgrind/memcheck-amd64-linux)
==16663==    by 0x1002A9994F: ???

sched status:
  running_tid=1

Thread 1: status = VgTs_Runnable (lwpid 16663)
==16663==    at 0x401CBE5: ??? (in /usr/lib/x86_64-linux-gnu/ld-2.31.so)
==16663==    by 0x1F8BFBFE: ???


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
For valgrind to run as expected

SOFTWARE/OS VERSIONS
Windows: 10
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
The c program compiled just has a printf statement in it.
sudo apt-get install valgrind gives: "valgrind is already the newest version (1:3.15.0-1ubuntu9.1)."
Comment 1 Tom Hughes 2021-10-07 08:41:54 UTC

*** This bug has been marked as a duplicate of bug 419562 ***