From: Jan Vrany <jan.vrany@labware.com>
To: gdb-patches@sourceware.org
Cc: Jan Vrany <jan.vrany@labware.com>
Subject: [pushed] gdb: update is_addr_in_objfile to support "dynamic" objfiles
Date: Fri, 28 Nov 2025 13:49:50 +0000 [thread overview]
Message-ID: <20251128134950.1763596-4-jan.vrany@labware.com> (raw)
In-Reply-To: <20251128134950.1763596-1-jan.vrany@labware.com>
While working with objfiles in Python I noticed that
gdb.Progspace.objfile_for_address () does not return "dynamic" objfiles
created by (for example) GDB's JIT reader API.
This is because is_addr_in_objfile() checks if a given address falls into
any (mappped) section of that objfile. However objfiles created by JIT
reader API do not have sections.
To solve this issue, this commit updates is_addr_in_objfile() to also
check if the address fall into any compunit in that objfile. It does so
only if the objfile has no sections.
---
gdb/objfiles.c | 24 +++++++++++++++++++-----
gdb/objfiles.h | 2 +-
gdb/symtab.c | 8 ++++++++
gdb/symtab.h | 3 +++
gdb/testsuite/gdb.base/jit-reader.exp | 9 +++++++++
5 files changed, 40 insertions(+), 6 deletions(-)
diff --git a/gdb/objfiles.c b/gdb/objfiles.c
index 0d166ceec4c..5c5b04c6458 100644
--- a/gdb/objfiles.c
+++ b/gdb/objfiles.c
@@ -1084,14 +1084,28 @@ is_addr_in_objfile (CORE_ADDR addr, const struct objfile *objfile)
if (objfile == NULL)
return false;
- for (obj_section &osect : objfile->sections ())
+ if (objfile->sections_start == nullptr)
{
- if (section_is_overlay (&osect) && !section_is_mapped (&osect))
- continue;
+ /* Objfiles created dynamically by the JIT reader API (and possibly by
+ other means too) do not have sections. For such "dynamic" objfiles
+ walk over all compunits and check if any of them contains given
+ ADDR. */
+ for (const compunit_symtab &cu : objfile->compunits ())
+ if (cu.contains (addr))
+ return true;
+ }
+ else
+ {
+ for (obj_section &osect : objfile->sections ())
+ {
+ if (section_is_overlay (&osect) && !section_is_mapped (&osect))
+ continue;
- if (osect.contains (addr))
- return true;
+ if (osect.contains (addr))
+ return true;
+ }
}
+
return false;
}
diff --git a/gdb/objfiles.h b/gdb/objfiles.h
index 0dd3fafac03..f65f3bde930 100644
--- a/gdb/objfiles.h
+++ b/gdb/objfiles.h
@@ -476,7 +476,7 @@ struct objfile : intrusive_list_node<objfile>
/* A range adapter that makes it possible to iterate over all
compunits in one objfile. */
- compunit_symtab_range compunits ()
+ compunit_symtab_range compunits () const
{
auto begin = compunit_symtab_iterator (compunit_symtabs.begin ());
auto end = compunit_symtab_iterator (compunit_symtabs.end ());
diff --git a/gdb/symtab.c b/gdb/symtab.c
index 701aa5d0007..5754d944b6c 100644
--- a/gdb/symtab.c
+++ b/gdb/symtab.c
@@ -513,6 +513,14 @@ compunit_symtab::symbol_at_address (CORE_ADDR addr) const
/* See symtab.h. */
+bool
+compunit_symtab::contains (CORE_ADDR addr) const
+{
+ return blockvector ()->contains (addr);
+}
+
+/* See symtab.h. */
+
compunit_symtab::compunit_symtab (struct objfile *objfile,
const char *name_)
: m_objfile (objfile),
diff --git a/gdb/symtab.h b/gdb/symtab.h
index 33cf0a6c229..45aca07bc36 100644
--- a/gdb/symtab.h
+++ b/gdb/symtab.h
@@ -1964,6 +1964,9 @@ struct compunit_symtab : intrusive_list_node<compunit_symtab>
for ADDR are considered. */
struct symbol *symbol_at_address (CORE_ADDR addr) const;
+ /* True if ADDR is in this compunit_symtab, false otherwise. */
+ bool contains (CORE_ADDR addr) const;
+
/* Object file from which this symtab information was read. */
struct objfile *m_objfile;
diff --git a/gdb/testsuite/gdb.base/jit-reader.exp b/gdb/testsuite/gdb.base/jit-reader.exp
index cd844ca75d2..df2dd74a6ab 100644
--- a/gdb/testsuite/gdb.base/jit-reader.exp
+++ b/gdb/testsuite/gdb.base/jit-reader.exp
@@ -234,6 +234,15 @@ proc jit_reader_test {} {
gdb_test "python print( \[o for o in gdb.objfiles() if o.filename.startswith('<< JIT compiled code')\]\[0\].build_id )" \
"None" \
"python gdb.Objfile.build_id"
+
+ # Check that Progspace.objfile_for_address () finds "jitted"
+ # objfile
+ gdb_test "frame 0" \
+ "#0 $hex in jit_function_stack_mangle ()$any" \
+ "select frame 0"
+ gdb_test "python print( gdb.current_progspace().objfile_for_address(gdb.parse_and_eval('\$pc')) )" \
+ "<gdb.Objfile filename=<< JIT compiled code at $hex >>>" \
+ "python gdb.Progspace.objfile_for_address"
}
}
}
--
2.51.0
prev parent reply other threads:[~2025-11-28 14:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 13:49 [pushed] gdb: update blockvector::lookup Jan Vrany
2025-11-28 13:49 ` [pushed] gdb: change blockvector::contains() to handle blockvectors with "holes" Jan Vrany
2025-12-02 17:41 ` Tom Tromey
2025-12-02 21:58 ` Jan Vraný
2025-12-03 19:36 ` Tom Tromey
2025-12-03 21:31 ` Jan Vraný
2025-12-04 11:42 ` Tom de Vries
2025-12-04 15:03 ` Jan Vraný
2025-11-28 13:49 ` [pushed] gdb: add unittests for blockvector lookup functions Jan Vrany
2025-11-28 13:49 ` Jan Vrany [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251128134950.1763596-4-jan.vrany@labware.com \
--to=jan.vrany@labware.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox