https://bugs.kde.org/show_bug.cgi?id=496468

            Bug ID: 496468
           Summary: valgrind: mmap(0x400000, 8192) failed in UME with
                    error 22 (Invalid argument). valgrind: this can be
                    caused by executables with very large text, data or
                    bss segments.
    Classification: Developer tools
           Product: valgrind
           Version: 3.24 GIT
          Platform: RedHat Enterprise Linux
                OS: Linux
            Status: REPORTED
          Severity: crash
          Priority: NOR
         Component: general
          Assignee: jsew...@acm.org
          Reporter: satishs.kam...@gmail.com
  Target Milestone: ---

SUMMARY
```
[satishk@tcn3 temp]$ valgrind ./core_avx2.out
valgrind: mmap(0x400000, 4096) failed in UME with error 22 (Invalid argument).
valgrind: this can be caused by executables with very large text, data or bss
segments.
[satishk@tcn3 temp]$ size core_avx2.out
   text    data     bss     dec     hex filename
   1831     560       1    2392     958 core_avx2.out
[satishk@tcn3 temp]$
```


STEPS TO REPRODUCE
1. running valgrind on any executable is resulting in this.
2. 
3. 

OBSERVED RESULT
```
[satishk@tcn3 temp]$ valgrind -d ./core_avx2.out
--1960444:1:debuglog DebugLog system started by Stage 1, level 1 logging
requested
--1960444:1:launcher no tool requested, defaulting to 'memcheck'
--1960444:1:launcher selected platform 'amd64-linux'
--1960444:1:launcher launching
/sw/arch/RHEL9/EB_production/2024/software/Valgrind/3.24.0-gompi-2024a/libexec/valgrind/memcheck-amd64-linux
--1960444:1:debuglog DebugLog system started by Stage 2 (main), level 1 logging
requested
--1960444:1:    main Welcome to Valgrind version 3.24.0 debug logging
--1960444:1:    main Checking current stack is plausible
--1960444:1:    main Checking initial stack was noted
--1960444:1:    main Starting the address space manager
--1960444:1:    main Address space manager is running
--1960444:1:    main Starting the dynamic memory manager
--1960444:1:mallocfr newSuperblock at 0x1002001000 (pszB 4194272)  owner
VALGRIND/core
--1960444:1:mallocfr deferred_reclaimSuperblock at 0x1002001000 (pszB 4194272) 
(prev 0x0) owner VALGRIND/core
--1960444:1:    main Dynamic memory manager is running
--1960444:1:    main Initialise m_debuginfo
--1960444:1:    main VG_(libdir) =
/sw/arch/RHEL9/EB_production/2024/software/Valgrind/3.24.0-gompi-2024a/libexec/valgrind
--1960444:1:    main Getting launcher's name ...
--1960444:1:    main ...
/gpfs/admin/_hpc/sw/arch/AMD-ZEN2/RHEL9/EB_production/2024/software/Valgrind/3.24.0-gompi-2024a/bin/valgrind
--1960444:1:    main Get hardware capabilities ...
--1960444:1:   cache Autodetected cache info is sensible
--1960444:1:   cache Cache info:
--1960444:1:   cache   #levels = 3
--1960444:1:   cache   #caches = 4
--1960444:1:   cache      cache #0:
--1960444:1:   cache         kind = data
--1960444:1:   cache         level = 1
--1960444:1:   cache         size = 32768 bytes
--1960444:1:   cache         linesize = 64 bytes
--1960444:1:   cache         assoc = 8
--1960444:1:   cache      cache #1:
--1960444:1:   cache         kind = insn
--1960444:1:   cache         level = 1
--1960444:1:   cache         size = 32768 bytes
--1960444:1:   cache         linesize = 64 bytes
--1960444:1:   cache         assoc = 8
--1960444:1:   cache      cache #2:
--1960444:1:   cache         kind = unified
--1960444:1:   cache         level = 2
--1960444:1:   cache         size = 524288 bytes
--1960444:1:   cache         linesize = 64 bytes
--1960444:1:   cache         assoc = 8
--1960444:1:   cache      cache #3:
--1960444:1:   cache         kind = unified
--1960444:1:   cache         level = 3
--1960444:1:   cache         size = 268435456 bytes
--1960444:1:   cache         linesize = 64 bytes
--1960444:1:   cache         assoc = 1
--1960444:1:    main ... arch = AMD64, hwcaps =
amd64-cx16-lzcnt-rdtscp-sse3-ssse3-avx-avx2-bmi-f16c-rdrand-rdseed-fma
--1960444:1:    main Getting the working directory at startup
--1960444:1:    main ... /gpfs/home5/satishk/temp
--1960444:1:    main Split up command line
--1960444:1:    main (early_) Process Valgrind's command line options
--1960444:1:    main Create initial image
--1960444:1: initimg Loading client
valgrind: mmap(0x400000, 4096) failed in UME with error 22 (Invalid argument).
valgrind: this can be caused by executables with very large text, data or bss
segments.

```

EXPECTED RESULT


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
```
[satishk@tcn3 temp]$ cat /etc/os-release
NAME="Red Hat Enterprise Linux"
VERSION="9.4 (Plow)"
ID="rhel"
ID_LIKE="fedora"
VERSION_ID="9.4"
PLATFORM_ID="platform:el9"
PRETTY_NAME="Red Hat Enterprise Linux 9.4 (Plow)"
ANSI_COLOR="0;31"
LOGO="fedora-logo-icon"
CPE_NAME="cpe:/o:redhat:enterprise_linux:9::baseos"
HOME_URL="https://www.redhat.com/";
DOCUMENTATION_URL="https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9";
BUG_REPORT_URL="https://bugzilla.redhat.com/";

REDHAT_BUGZILLA_PRODUCT="Red Hat Enterprise Linux 9"
REDHAT_BUGZILLA_PRODUCT_VERSION=9.4
REDHAT_SUPPORT_PRODUCT="Red Hat Enterprise Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="9.4"
[satishk@tcn3 temp]$ uname -r
5.14.0-427.31.1.el9_4.x86_64
```
ADDITIONAL INFORMATION: Even though the executable is a bare and a dummy
program with one function valgrind crashes with that error. Valgrind was built
with Easybuild.
The configure statement for the installation:
```
== 2024-11-14 11:22:09,009 run.py:260 INFO running cmd:  ./configure
--prefix=/sw/arch/RHEL9/EB_production/2024/software/Valgrind/3.24.0-gompi-2024a
 --build=x86_64-pc-linux-gnu  --host=x86_64-pc-linux-gnu  --with-mpicc="$MPICC" 
```

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to