diff options
| author | Georgii Rymar <grimar@accesssoftek.com> | 2020-12-04 11:54:03 +0300 |
|---|---|---|
| committer | Georgii Rymar <grimar@accesssoftek.com> | 2020-12-16 12:59:32 +0300 |
| commit | 78aea98308a85c061a87952e9842bf1e6fe097d5 (patch) | |
| tree | 7996cbd5e1cc88706741016ed51aa5d1f4ffa695 /llvm/tools/llvm-objdump/llvm-objdump.cpp | |
| parent | 0da240c2d050303c99564f1901b0d1548ffe2323 (diff) | |
| download | llvm-78aea98308a85c061a87952e9842bf1e6fe097d5.zip llvm-78aea98308a85c061a87952e9842bf1e6fe097d5.tar.gz llvm-78aea98308a85c061a87952e9842bf1e6fe097d5.tar.bz2 | |
[llvm-readelf/obj] - Handle out-of-order PT_LOADs better.
This is https://bugs.llvm.org/show_bug.cgi?id=45698.
Specification says that
"Loadable segment entries in the program header table appear
in ascending order, sorted on the p_vaddr member."
Our `toMappedAddr()` relies on this condition. This patch
adds a warning when the sorting order of loadable segments is wrong.
In this case we force segments sorting and that allows
`toMappedAddr()` to work as expected.
Differential revision: https://reviews.llvm.org/D92641
Diffstat (limited to 'llvm/tools/llvm-objdump/llvm-objdump.cpp')
0 files changed, 0 insertions, 0 deletions