From: Alvaro K. <ku...@gm...> - 2021-09-06 02:39:31
|
My program is very simple: they are exercises from a course about ADT (Abstract Data Types). On Sun, Sep 5, 2021 at 11:24 PM John Borland < all...@gm...> wrote: > if you have a lot of threads you can try the fair scheduler flag. > > On Sun, Sep 5, 2021, 8:59 PM John Reiser <jr...@bi...> wrote: > >> > 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 >> [[snip]] >> > >> > What could be the problem? GGC 11 perhaps? >> >> There have been some hints of trouble with the DWARF-5 symbol reader. >> Thus a work-around might be to avoid DWARF-5 by using an older gcc. >> >> If you can, please run "perf record" and then "perf report", >> and copy+paste (or attach) info into a Bug Report (see >> https://valgrind.org). >> Then post the bug link here with a teaser. >> >> >> >> _______________________________________________ >> Valgrind-users mailing list >> Val...@li... >> https://lists.sourceforge.net/lists/listinfo/valgrind-users >> > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users > |