public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug gdb/30581] New: Improving the JIT Interface
@ 2023-06-23 11:50 admin at typoflash dot com
0 siblings, 0 replies; only message in thread
From: admin at typoflash dot com @ 2023-06-23 11:50 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=30581
Bug ID: 30581
Summary: Improving the JIT Interface
Product: gdb
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: admin at typoflash dot com
Target Milestone: ---
From my understanding of the code, to load ELF debug symbols with the JIT
interface, the DWARF pc values must point to absolute addresses. Thus it is not
possible to e.g. use the interface with compiler-generated shared ELF
libraries.
This is due to:
1. "jit_bfd_try_read_symtab" stores the sections sec->sh_addr into sai.
2. "addr_info_make_relative" substracts the sec->sh_addr from the sai address,
making the sai addresses zero.
3. "relative_addr_info_to_section_offsets" sets the section_offsets to the zero
sai addresses.
4. "read_func_scope" takes a zero base address from section_offsets when
resolving a symbol address.
I assume the JIT ELF files are supposed to be created with absolute DWARF pc
values and the text sec->sh_addr values don't matter?
This incompatibility between regular and generated ELF files for the JIT
interface seems odd.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2023-06-23 11:51 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-06-23 11:50 [Bug gdb/30581] New: Improving the JIT Interface admin at typoflash dot com
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).