https://bugs.kde.org/show_bug.cgi?id=469783
Bug ID: 469783
Summary: ARM32: Process terminating with default action of
signal 11 (SIGSEGV): _dl_discover_osversion (in
/lib/ld-linux-armhf.so.3)
Classification: Developer tools
Product: valgrind
Version: 3.17.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: memcheck
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
On ARM32 (ALT Linux) any tool of valgrind (even `none`) reports SIGSEGV and
crashes target binary (which is perfectly working otherwise):
```
# valgrind --tool=none ls
==2125518== Nulgrind, the minimal Valgrind tool
==2125518== Copyright (C) 2002-2017, and GNU GPL'd, by Nicholas Nethercote.
==2125518== Using Valgrind-3.17.0 and LibVEX; rerun with -h for copyright info
==2125518== Command: ls
==2125518==
==2125518==
==2125518== Process terminating with default action of signal 11 (SIGSEGV)
==2125518== Access not within mapped region at address 0xFEB7FFAC
==2125518== at 0x4012068: _dl_discover_osversion (in
/lib/ld-linux-armhf.so.3)
==2125518== If you believe this happened as a result of a stack
==2125518== overflow in your program's main thread (unlikely but
==2125518== possible), you can try to increase the size of the
==2125518== main thread stack using the --main-stacksize= flag.
==2125518== The main thread stack size used in this run was 8388608.
==2125518==
Segmentation fault
```
When run under another user reported function is different:
```
$ valgrind --tool=none ls
==2127882== Nulgrind, the minimal Valgrind tool
==2127882== Copyright (C) 2002-2017, and GNU GPL'd, by Nicholas Nethercote.
==2127882== Using Valgrind-3.17.0 and LibVEX; rerun with -h for copyright info
==2127882== Command: ls
==2127882==
==2127882==
==2127882== Process terminating with default action of signal 11 (SIGSEGV):
dumping core
==2127882== Access not within mapped region at address 0xFE8D325C
==2127882== at 0x40134B8: handle_preload_list (in /lib/ld-linux-armhf.so.3)
==2127882== If you believe this happened as a result of a stack
==2127882== overflow in your program's main thread (unlikely but
==2127882== possible), you can try to increase the size of the
==2127882== main thread stack using the --main-stacksize= flag.
==2127882== The main thread stack size used in this run was 8388608.
==2127882==
Segmentation fault
```
```
/# ls
bin boot dev etc home lib media mnt opt proc root run sbin selinux
srv sys tmp usr var
```
--
You are receiving this mail because:
You are watching all bug changes.
