[valgrind] [Bug 442061] Valgrind: very slow execution under Fedora 34

2021-09-06 Thread Alvaro Kuolas 
https://bugs.kde.org/show_bug.cgi?id=442061

--- Comment #4 from Alvaro Kuolas  ---
I want to clarify that I installed debuginfo to try gdb reverse-step.

The packages installed where:

dnf install debuginfo-install glibc-2.33-20.fc34.x86_64
libgcc-11.2.1-1.fc34.x86_64 libstdc++-11.2.1-1.fc34.x86_64 

Without the debuginfo packages it works as expected.

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

[valgrind] [Bug 442061] Valgrind: very slow execution under Fedora 34

2021-09-05 Thread Alvaro Kuolas 
https://bugs.kde.org/show_bug.cgi?id=442061

Alvaro Kuolas  changed:

   What|Removed |Added

 CC||kuo...@gmail.com

--- Comment #1 from Alvaro Kuolas  ---
Created attachment 141323
  --> https://bugs.kde.org/attachment.cgi?id=141323=edit
perf record data

Attached is perf record data

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

[valgrind] [Bug 442061] New: Valgrind: very slow execution under Fedora 34

2021-09-05 Thread Alvaro Kuolas 
https://bugs.kde.org/show_bug.cgi?id=442061

Bug ID: 442061
   Summary: Valgrind: very slow execution under Fedora 34
   Product: valgrind
   Version: unspecified
  Platform: Fedora RPMs
OS: All
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: kuo...@gmail.com
  Target Milestone: ---

SUMMARY

I am running valgrind on my PC with dual boot Windows 10 and Fedora 34.

Running the same test on Ubuntu 20.04 (under Windows 10 WSL2) valgrind runs in
less than a second, but on Fedora 34 is very slow, several minutes slow.

On Fedora 34 it looks like the time spent is reading symbols.

This is the part that takes most of the time:

--23524-- Reading syms from /usr/lib64/libstdc++.so.6.0.29
--23524--   Considering
/usr/lib/debug/.build-id/bd/d633ff5da0bba64d19ecf277a9eed7001da127.debug ..
--23524--   .. build-id is valid
--23524--   Considering
/usr/lib/debug/.build-id/bd/../../../../../usr/lib/debug/usr/lib64/../../.dwz/gcc-11.2.1-1.fc34.x86_64
..
--23524--   .. build-id is valid
--23524-- Reading syms from /usr/lib64/libm-2.33.so
--23524--   Considering
/usr/lib/debug/.build-id/c1/784bbe8a93a6e62f74b16105a2076a03b398ac.debug ..
--23524--   .. build-id is valid
--23524-- Reading syms from /usr/lib64/libgcc_s-11-20210728.so.1
--23524--   Considering
/usr/lib/debug/.build-id/46/e10c9ee769c5cfc7cdb638e3ccbc3169c0a949.debug ..
--23524--   .. build-id is valid
--23524--   Considering
/usr/lib/debug/.build-id/46/../../../../../usr/lib/debug/lib64/../.dwz/gcc-11.2.1-1.fc34.x86_64
..
--23524--   .. build-id is valid
--23524-- Reading syms from /usr/lib64/libc-2.33.so
--23524--   Considering
/usr/lib/debug/.build-id/9d/e0f6e78ec16db4c6c167efc6b37466705edeff.debug ..
--23524--   .. build-id is valid
--23524--   Considering
/usr/lib/debug/.build-id/9d/../../../../../usr/lib/debug/lib64/../.dwz/glibc-2.33-20.fc34.x86_64
..
--23524--   .. build-id is valid



STEPS TO REPRODUCE
1. Run valgrind on a simple binary 

OBSERVED RESULT
It takes minutes to execute.

EXPECTED RESULT
It should be instant as the program is very simple like "hello world".

SOFTWARE/OS VERSIONS
Linux: 5.13.13-200.fc34.x86_64 #1 SMP Thu Aug 26 17:06:39 UTC 2021 x86_64
x86_64 x86_64 GNU/Linux


ADDITIONAL INFORMATION
Using GCC 11

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