https://sourceware.org/bugzilla/show_bug.cgi?id=30975
Mark Wielaard changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://sourceware.org/bugzilla/show_bug.cgi?id=30975
--- Comment #7 from Aaron Merey ---
(In reply to Pablo Galindo Salgado from comment #6)
> Hi, I can confirm that this indeed fixes the issue. Thanks to everyone
> involved. Fantastic work!
Thanks Pablo, glad to hear!
--
You are receiving th
https://sourceware.org/bugzilla/show_bug.cgi?id=30975
--- Comment #6 from Pablo Galindo Salgado ---
Hi, I can confirm that this indeed fixes the issue. Thanks to everyone
involved. Fantastic work!
--
You are receiving this mail because:
You are on the CC list for the bug.
https://sourceware.org/bugzilla/show_bug.cgi?id=30975
--- Comment #5 from Aaron Merey ---
A fix for this bug has been merged into elfutils upstream in commit
2f38fa57942f9. I'm going to leave this bug open for now while the patch makes
its way into Fedora and RHEL.
Pablo if you get a chance, ple
https://sourceware.org/bugzilla/show_bug.cgi?id=30975
--- Comment #4 from Aaron Merey ---
(In reply to Aaron Merey from comment #3)
> Patch posted to elfutils-devel@
>
> https://sourceware.org/pipermail/elfutils-devel/2023q4/006644.html
I should also clarify that this patch just prevents eager
https://sourceware.org/bugzilla/show_bug.cgi?id=30975
Aaron Merey changed:
What|Removed |Added
Assignee|unassigned at sourceware dot org |amerey at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=30975
--- Comment #2 from Pablo Galindo Salgado ---
Maybe a first attempt to improve the situation could be to not eagerly remove
"colliding" modules but either warn or take a callback to act on them or some
way to deactivate that behavior as curren
https://sourceware.org/bugzilla/show_bug.cgi?id=30975
Mark Wielaard changed:
What|Removed |Added
Last reconfirmed||2023-11-02
Status|UNCONFI
