https://bugs.kde.org/show_bug.cgi?id=471807
--- Comment #21 from Carl Love ---
I tested the patch on PowerPC BE. Test results:
Power 8 BE Ubuntu 20.04.5 LTS (Focal Fossa)
pre-lazy-load with Explicitly-load- initialize opd_escn
(as of 8/31/2023)
https://bugs.kde.org/show_bug.cgi?id=471807
--- Comment #20 from Carl Love ---
Aaron created a patch to fix the BE failures. It was sent out on Monday Sept
18, subject Re: [Valgrind-developers] ppc64le results
>From 626b205bb9fbe209353b708ace7b22644ca0607a Mon Sep 17 00:00:00 2001
From: Aaron M
https://bugs.kde.org/show_bug.cgi?id=471807
--- Comment #19 from Carl Love ---
The ppc patch was tested on a variety of Power Platforms. Here is what I am
seeing before the commit to add the lazy loading,
with the current Valgrind mainline (includes the lazy commit) and with the
patch to fix t
https://bugs.kde.org/show_bug.cgi?id=471807
--- Comment #18 from Aaron Merey ---
Created attachment 161290
--> https://bugs.kde.org/attachment.cgi?id=161290&action=edit
ppc fix
I've attached a patch that should fix the ppc regressions. I posted it to the
valgrind-developers list and I'm also p
https://bugs.kde.org/show_bug.cgi?id=471807
Carl Love changed:
What|Removed |Added
CC||c...@us.ibm.com
--- Comment #17 from Carl Love ---
https://bugs.kde.org/show_bug.cgi?id=471807
--- Comment #16 from Mark Wielaard ---
This did create some regressions on linux-ppc64le:
memcheck/tests/inlinfo (stderr)
memcheck/tests/inlinfosupp (stderr)
memcheck/tests/inlinfosuppobj(stderr)
memcheck/tes
https://bugs.kde.org/show_bug.cgi?id=471807
--- Comment #15 from Mark Wielaard ---
Note there was one cleanup followup for an error case:
commit a0d555a0dfe078ef04ea49d991a8090ab14bd4a5
Author: Paul Floyd
Date: Sat Aug 19 21:37:33 2023 +0200
Always cleanup on exit from ML_(read_elf_objec
https://bugs.kde.org/show_bug.cgi?id=471807
--- Comment #14 from Mark Wielaard ---
I have seen no regressions from this patch. At least not in the nightly tests.
There was one issue on s390x. drd/tests/getaddrinfo would randomly fail (one in
~5 times).
But this can also be replicated when reverti
https://bugs.kde.org/show_bug.cgi?id=471807
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=471807
Aaron Merey changed:
What|Removed |Added
Attachment #160848|0 |1
is obsolete|
https://bugs.kde.org/show_bug.cgi?id=471807
Mark Wielaard changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=471807
Aaron Merey changed:
What|Removed |Added
Attachment #160636|0 |1
is obsolete|
https://bugs.kde.org/show_bug.cgi?id=471807
--- Comment #9 from Mark Wielaard ---
(In reply to Aaron Merey from comment #8)
> (In reply to Mark Wielaard from comment #6)
> > Do we need a --enable-lazy-debuginfo=[yes|no] flag?
> > Is there any advantage to the user to set it to no?
> > Less varian
https://bugs.kde.org/show_bug.cgi?id=471807
Aaron Merey changed:
What|Removed |Added
Attachment #160375|0 |1
is obsolete|
https://bugs.kde.org/show_bug.cgi?id=471807
--- Comment #7 from Mark Wielaard ---
v3 does work. But I admit to not fully understand why/how.
The addr_load_di calls in coregrind/m_stacktrace..c seems unnecessary (you can
comment them out and things still work fine).
This is because there is a addr
https://bugs.kde.org/show_bug.cgi?id=471807
--- Comment #6 from Mark Wielaard ---
Do we need a --enable-lazy-debuginfo=[yes|no] flag?
Is there any advantage to the user to set it to no?
Less variants in the code seems good.
--
You are receiving this mail because:
You are watching all bug change
https://bugs.kde.org/show_bug.cgi?id=471807
Aaron Merey changed:
What|Removed |Added
Attachment #160259|0 |1
is obsolete|
https://bugs.kde.org/show_bug.cgi?id=471807
--- Comment #4 from Mark Wielaard ---
(In reply to Aaron Merey from comment #3)
> Created attachment 160259 [details]
> patch-v2
>
> I've updated the patch with lazy debuginfo support for all ELF platforms. I
> regression tested this on Fedora 38 x86_6
https://bugs.kde.org/show_bug.cgi?id=471807
Aaron Merey changed:
What|Removed |Added
Attachment #160009|0 |1
is obsolete|
https://bugs.kde.org/show_bug.cgi?id=471807
--- Comment #2 from Aaron Merey ---
(In reply to Mark Wielaard from comment #1)
> (In reply to Aaron Merey from comment #0)
> > Currently only AMD64 Linux is supported.
>
> Why is that? The patch looks generic for ELF platforms. Is there something
> sp
https://bugs.kde.org/show_bug.cgi?id=471807
Mark Wielaard changed:
What|Removed |Added
CC||m...@klomp.org
--- Comment #1 from Mark Wielaar
https://bugs.kde.org/show_bug.cgi?id=471807
Aaron Merey changed:
What|Removed |Added
CC||ame...@redhat.com
--
You are receiving this mail
22 matches
Mail list logo
