https://bugs.kde.org/show_bug.cgi?id=433500
Mark Wielaard <m...@klomp.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #8 from Mark Wielaard <m...@klomp.org> ---
(In reply to Paul Floyd from comment #7)
> The testcase passes with a time 0f 60s. But it fails still with 50s. The
> value is likely to be machine dependent - my PC is pretty old though.
>
> Intel(R) Xeon(R) CPU W3520 @ 2.67GHz
>
> About 10 years old.
If the test passes the timeout doesn't really matter. Lets set it to 60 if that
guarantees it passes even on old hardware.
We do have to look at the slowness of the debuginfo parsing.
I also noticed it with the debuginfod support.
But this particular issue seems to be solved by:
Make the dwarf3 reader more robust and less chatty when things go wrong
Skip some stuff when seeing an unknown language, be less chatty about
parser issues.
All the issues seem to come from the multi-file, that is the shared
(supplementary or alt) file containing debuginfo shared by all the
gcc/runtime libraries.
There are a couple of issues that this patch works around:
- The multifile contains entries for the 'D' language, which has some
constructs we don't expect.
- We don't read partial units correctly, which means we often don't know
the language we are looking at.
- The parser is very chatty about issues it didn't expect (even if they
are ignored, it will still output something)
It only shows up with --read-var-info=yes which some tests enable, but
which is disabled by default.
Also increate the timeout of drd/tests/pth_cleanup_handler.c because
DWARF reading is so slow.
https://bugs.kde.org/show_bug.cgi?id=433500
--
You are receiving this mail because:
You are watching all bug changes.
