[valgrind] [Bug 390871] ELF debug info reader confused with multiple .rodata* sections

2023-10-08 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=390871 Paul Floyd changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED

[valgrind] [Bug 390871] ELF debug info reader confused with multiple .rodata* sections

2023-10-08 Thread Tyson Nottingham
https://bugs.kde.org/show_bug.cgi?id=390871 --- Comment #14 from Tyson Nottingham --- (In reply to Paul Floyd from comment #12) > I pushed a change, cold you confirm that it is ok? Yes, it appears to resolve the problem. -- You are receiving this mail because: You are watching all bug

[valgrind] [Bug 390871] ELF debug info reader confused with multiple .rodata* sections

2023-10-08 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=390871 --- Comment #13 from Paul Floyd --- (and for John, sorry I mistyped your name in git commit --author) -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 390871] ELF debug info reader confused with multiple .rodata* sections

2023-10-08 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=390871 --- Comment #12 from Paul Floyd --- Not sure what's missing. With Fedora 38 I get Compiling valgrind-ebpf-rodata-bug v0.1.0 (/home/paulf/valgrind-ebpf-rodata-bug) error: failed to run custom build command for `valgrind-ebpf-rodata-bug v0.1.0

[valgrind] [Bug 390871] ELF debug info reader confused with multiple .rodata* sections

2023-10-07 Thread Sam James
https://bugs.kde.org/show_bug.cgi?id=390871 Sam James changed: What|Removed |Added CC||s...@gentoo.org -- You are receiving this mail

[valgrind] [Bug 390871] ELF debug info reader confused with multiple .rodata* sections

2023-10-07 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=390871 --- Comment #11 from Paul Floyd --- (In reply to Tyson Nottingham from comment #10) > Sure, though I'm only able to give repro steps geared towards Ubuntu. > > https://github.com/tgnottingham/valgrind-ebpf-rodata-bug OK thanks, I'll try to test it

[valgrind] [Bug 390871] ELF debug info reader confused with multiple .rodata* sections

2023-10-07 Thread Tyson Nottingham
https://bugs.kde.org/show_bug.cgi?id=390871 --- Comment #10 from Tyson Nottingham --- (In reply to Paul Floyd from comment #8) > (In reply to Tyson Nottingham from comment #7) > > I ran into this issue when compiling a Rust program that uses eBPF with the > > mold linker. > > Can you provide an

[valgrind] [Bug 390871] ELF debug info reader confused with multiple .rodata* sections

2023-10-07 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=390871 --- Comment #9 from Paul Floyd --- The problem seems to have gone away on Solaris. GCC has dropped Solaris 11.3, and the latest build I have is g++ (GCC) 12.0.1 20220425 (experimental) Syill, the patch looks good so I'll test it and push if it

[valgrind] [Bug 390871] ELF debug info reader confused with multiple .rodata* sections

2023-10-06 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=390871 --- Comment #8 from Paul Floyd --- (In reply to Tyson Nottingham from comment #7) > I ran into this issue when compiling a Rust program that uses eBPF with the > mold linker. Can you provide an example? Since I originally reported this I can test of

[valgrind] [Bug 390871] ELF debug info reader confused with multiple .rodata* sections

2023-10-06 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=390871 Paul Floyd changed: What|Removed |Added Assignee|jsew...@acm.org |pjfl...@wanadoo.fr -- You are receiving this

[valgrind] [Bug 390871] ELF debug info reader confused with multiple .rodata* sections

2023-10-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=390871 tgnotting...@gmail.com changed: What|Removed |Added CC||tgnotting...@gmail.com --- Comment #7

[valgrind] [Bug 390871] ELF debug info reader confused with multiple .rodata* sections

2018-08-06 Thread John Reiser
https://bugs.kde.org/show_bug.cgi?id=390871 --- Comment #6 from John Reiser --- I believe that this bug and revised patch still are valid. The intervening https://bugs.kde.org/show_bug.cgi?id=395682#c9 is a distinct issue regarding .rodata for multiple segments. That bug does not address the

[valgrind] [Bug 390871] ELF debug info reader confused with multiple .rodata* sections

2018-08-06 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=390871 --- Comment #5 from Julian Seward --- Is this still valid, considering there's been at least one related fix to the debuginfo reader recently? -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 390871] ELF debug info reader confused with multiple .rodata* sections

2018-07-16 Thread John Reiser
https://bugs.kde.org/show_bug.cgi?id=390871 --- Comment #4 from John Reiser --- Created attachment 113979 --> https://bugs.kde.org/attachment.cgi?id=113979=edit .rodata*: aggregate multiple adjacent sections after alignment Revise (and obsolete) the previous patch because of the intervening

[valgrind] [Bug 390871] ELF debug info reader confused with multiple .rodata* sections

2018-07-16 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=390871 Mark Wielaard changed: What|Removed |Added CC||m...@klomp.org --- Comment #3 from Mark

[valgrind] [Bug 390871] ELF debug info reader confused with multiple .rodata* sections

2018-07-11 Thread Florian Weimer
https://bugs.kde.org/show_bug.cgi?id=390871 Florian Weimer changed: What|Removed |Added CC||fwei...@redhat.com -- You are receiving this

[valgrind] [Bug 390871] ELF debug info reader confused with multiple .rodata* sections

2018-06-05 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=390871 --- Comment #2 from Paul Floyd --- Mail from Rainer Orth on GCC mailing list those sections are in libstdc++.so. They can be found in the input objects used to created libstdc++.so on Linux and Solaris alike, due to the use of -fdata-sections (via

[valgrind] [Bug 390871] ELF debug info reader confused with multiple .rodata* sections

2018-06-02 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=390871 Paul Floyd changed: What|Removed |Added CC||pa...@free.fr --- Comment #1 from Paul Floyd ---