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=396476
H.J. Lu changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED |CON
https://bugs.kde.org/show_bug.cgi?id=396476
Bug ID: 396476
Summary: Reading debug info of binaries with zero-size PT_LOAD
segment
Product: valgrind
Version: 3.14 SVN
Platform: Other
OS: Linux
Sta
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
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 #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
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=379525
--- Comment #21 from H.J. Lu ---
(In reply to Julian Seward from comment #20)
> (In reply to Tanya from comment #17)
> > Would it be possible to patch the 32-bit instruction parser as well?
>
> I saw that part in your patch, but didn't land it, because
https://bugs.kde.org/show_bug.cgi?id=379525
--- Comment #16 from H.J. Lu ---
(In reply to Ivo Raisr from comment #14)
> And this is a minimalistic reproducer with the latest Valgrind sources:
>
> --
> #include
>
> int main ()
> {
> __asm__ __volatile__ (".byte 0x65, 0x0
https://bugs.kde.org/show_bug.cgi?id=379525
--- Comment #3 from H.J. Lu ---
(In reply to Julian Seward from comment #2)
> HJ, what's the use case here? Where are these coming from?
> Not from gcc-7.x AFAICT. So .. where?
NOP opcodes are turned into real instructions on new processors
from time
https://bugs.kde.org/show_bug.cgi?id=379525
Bug ID: 379525
Summary: Support more x86 nop opcodes
Product: valgrind
Version: 3.13 SVN
Platform: unspecified
OS: Linux
Status: UNCONFIRMED
Severity: normal
15 matches
Mail list logo
