https://bugs.kde.org/show_bug.cgi?id=395682
Mark Wielaard changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=395682
Lubos Lunak changed:
What|Removed |Added
CC||l.lu...@kde.org
--
You are receiving this mail b
https://bugs.kde.org/show_bug.cgi?id=395682
Ivo Raisr changed:
What|Removed |Added
CC||ori...@gmx.fr
--- Comment #14 from Ivo Raisr ---
*
https://bugs.kde.org/show_bug.cgi?id=395682
--- Comment #13 from H.J. Lu ---
(In reply to Mark Wielaard from comment #12)
> yes, you are right, but isn't that a totally different case? Your example
> seems to have everything in a single rx segment and then a zero size rw
> segment.
>
> Is that s
https://bugs.kde.org/show_bug.cgi?id=395682
H.J. Lu changed:
What|Removed |Added
Blocks||396476
Referenced Bugs:
https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=395682
--- Comment #12 from Mark Wielaard ---
(In reply to H.J. Lu from comment #10)
> (In reply to Mark Wielaard from comment #9)
> > This patch fixes the issue with the reported binary in this bug and with the
> > i386 glibc ld.so created on fedora (when bui
https://bugs.kde.org/show_bug.cgi?id=395682
--- Comment #11 from H.J. Lu ---
Created attachment 113899
--> https://bugs.kde.org/attachment.cgi?id=113899&action=edit
A test
With the proposed fix:
[hjl@gnu-cfl-1 build-x86_64-linux]$ ./.in_place/memcheck-amd64-linux
/export/gnu/import/git/g
https://bugs.kde.org/show_bug.cgi?id=395682
--- Comment #10 from H.J. Lu ---
(In reply to Mark Wielaard from comment #9)
> Created attachment 113898 [details]
> Accept read-only PT_LOAD segments and .rodata by ld -z separate-code
>
> I combined Tom's fix for separate read-only segments with the
https://bugs.kde.org/show_bug.cgi?id=395682
Mark Wielaard changed:
What|Removed |Added
Assignee|jsew...@acm.org |m...@klomp.org
--- Comment #9 from Mark Wielaar
https://bugs.kde.org/show_bug.cgi?id=395682
Tom Hughes changed:
What|Removed |Added
CC||t...@compton.nu
--- Comment #8 from Tom Hughes --
https://bugs.kde.org/show_bug.cgi?id=395682
H.J. Lu changed:
What|Removed |Added
Summary|Reading debug info of |Reading debug info of
|binaries lin
https://bugs.kde.org/show_bug.cgi?id=395682
H.J. Lu changed:
What|Removed |Added
Summary|Reading debug info of |Reading debug info of
|binaries lin
https://bugs.kde.org/show_bug.cgi?id=395682
--- Comment #6 from Mark Wielaard ---
(In reply to H.J. Lu from comment #5)
> (In reply to Mark Wielaard from comment #4)
> > The root cause is that ld -z separate-code introduces various new PT_LOAD
>
> This is very misleading.
I don't know why you s
https://bugs.kde.org/show_bug.cgi?id=395682
--- Comment #5 from H.J. Lu ---
(In reply to Mark Wielaard from comment #4)
> The root cause is that ld -z separate-code introduces various new PT_LOAD
This is very misleading. This simple test:
https://github.com/hjl-tools/simple-linux/tree/divide-b
https://bugs.kde.org/show_bug.cgi?id=395682
Mark Wielaard changed:
What|Removed |Added
Summary|Reading debug info |Reading debug info of
|
https://bugs.kde.org/show_bug.cgi?id=395682
H.J. Lu changed:
What|Removed |Added
CC||hjl.to...@gmail.com
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=395682
H.J. Lu changed:
What|Removed |Added
Version|unspecified |3.14 SVN
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=395682
Florian Weimer changed:
What|Removed |Added
CC||fwei...@redhat.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=395682
--- Comment #2 from Дилян Палаузов ---
For the time being programs can either be linked explicitly with gold:
gcc -fuse-ld=gold
or switch off the implicitly enabled separate-code on Linux/x86:
gcc -fuse-ld=bfd -Wl,-z,noseparate-code
or change the de
https://bugs.kde.org/show_bug.cgi?id=395682
--- Comment #1 from Дилян Палаузов ---
It turns out that when linking with ld.bfd 2.30 or gold 2.31.51.20180630) 1.16
valgrind can read the debug information, but not when ld.bfd 2.31.51.20180630
is used.
I described at https://sourceware.org/bugzilla/
20 matches
Mail list logo
