https://bugs.kde.org/show_bug.cgi?id=472409
Paul Floyd <pjfl...@wanadoo.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pjfl...@wanadoo.fr
--- Comment #1 from Paul Floyd <pjfl...@wanadoo.fr> ---
Can you tell what library libQt6Core is trying to load?
And if you can deternine that, can you get the program header with objdump -p,
for instance on amd64 RHEL 7.9 libm I get
/lib64/libm.so.6: file format elf64-x86-64
Program Header:
LOAD off 0x0000000000000000 vaddr 0x0000000000000000 paddr
0x0000000000000000 align 2**21
filesz 0x0000000000100834 memsz 0x0000000000100834 flags r-x
LOAD off 0x0000000000100d60 vaddr 0x0000000000300d60 paddr
0x0000000000300d60 align 2**21
filesz 0x0000000000000384 memsz 0x00000000000003d8 flags rw-
DYNAMIC off 0x0000000000100d80 vaddr 0x0000000000300d80 paddr
0x0000000000300d80 align 2**3
filesz 0x0000000000000230 memsz 0x0000000000000230 flags rw-
NOTE off 0x00000000000001c8 vaddr 0x00000000000001c8 paddr
0x00000000000001c8 align 2**2
filesz 0x0000000000000044 memsz 0x0000000000000044 flags r--
EH_FRAME off 0x00000000000f86a8 vaddr 0x00000000000f86a8 paddr
0x00000000000f86a8 align 2**2
filesz 0x000000000000122c memsz 0x000000000000122c flags r--
STACK off 0x0000000000000000 vaddr 0x0000000000000000 paddr
0x0000000000000000 align 2**4
filesz 0x0000000000000000 memsz 0x0000000000000000 flags rw-
RELRO off 0x0000000000100d60 vaddr 0x0000000000300d60 paddr
0x0000000000300d60 align 2**0
filesz 0x00000000000002a0 memsz 0x00000000000002a0 flags r--
What I'm interested in is the LOAD sections.
Valgrind has a fairly narrow (and hard-coded) loader. This works for the
defaults with GNU BFD ld and LLVM lld (and anything that generates the same
program header layout).
If you are using an incompatible link editor or linker scripts that change the
LOAD segments then that is likely to cause problems.
Secondly could you run Valgrind with -d -d -d ?
That will generate large amounts of output. The bit that I want to see should
look like
--6499-- di_notify_mmap-0:
--6499-- di_notify_mmap-1: 0x4028000-0x402cfff r--
--6499-- di_notify_mmap-2: /home/paulf/scratch/valgrind/drd/tests/dlopen_lib.so
--6499-- di_notify_mmap-3: is_rx_map 0, is_rw_map 0, is_ro_map 1
--6499-- di_notify_mmap-4: noting details in DebugInfo* at 0x10024C0590
--6499-- di_notify_mmap-6: no dinfo loaded
/home/paulf/scratch/valgrind/drd/tests/dlopen_lib.so (no rx or no rw mapping)
--6499-- di_notify_mmap-0:
--6499-- di_notify_mmap-1: 0x4029000-0x4029fff r-x
--6499-- di_notify_mmap-2: /home/paulf/scratch/valgrind/drd/tests/dlopen_lib.so
--6499-- di_notify_mmap-3: is_rx_map 1, is_rw_map 0, is_ro_map 0
--6499-- di_notify_mmap-4: noting details in DebugInfo* at 0x10024C0590
--6499-- di_notify_mmap-6: no dinfo loaded
/home/paulf/scratch/valgrind/drd/tests/dlopen_lib.so (no rx or no rw mapping)
--6499-- di_notify_mmap-0:
--6499-- di_notify_mmap-1: 0x402a000-0x402cfff r--
--6499-- di_notify_mmap-2: /home/paulf/scratch/valgrind/drd/tests/dlopen_lib.so
--6499-- di_notify_mmap-3: is_rx_map 0, is_rw_map 0, is_ro_map 1
--6499-- di_notify_mmap-4: noting details in DebugInfo* at 0x10024C0590
--6499-- di_notify_mmap-6: no dinfo loaded
/home/paulf/scratch/valgrind/drd/tests/dlopen_lib.so (no rx or no rw mapping)
--6499-- di_notify_mmap-0:
--6499-- di_notify_mmap-1: 0x402b000-0x402cfff rw-
--6499-- di_notify_mmap-2: /home/paulf/scratch/valgrind/drd/tests/dlopen_lib.so
--6499-- di_notify_mmap-3: is_rx_map 0, is_rw_map 1, is_ro_map 0
--6499-- di_notify_mmap-4: noting details in DebugInfo* at 0x10024C0590
--6499-- di_notify_mmap-5: achieved accept state for
/home/paulf/scratch/valgrind/drd/tests/dlopen_lib.so
--6499-- cfsi range rx-mappings coverage check: Covered 0x0-0xffffffffffffffff
(with a different path and shared library rather than dlopen_lib.so)
--
You are receiving this mail because:
You are watching all bug changes.
