[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH v5 08/14] gdb: Add functions to make loading from dynamically pos
From: |
Glenn Washburn |
Subject: |
[PATCH v5 08/14] gdb: Add functions to make loading from dynamically positioned targets easier |
Date: |
Fri, 23 Dec 2022 22:19:29 -0600 |
Many targets, such as EFI, load GRUB at addresses that are determined at
runtime. So the load addresses in kernel.exec will almost certainly be
wrong. Given the address of the start of the text segment, these
functions will tell GDB to load the symbols at the proper locations. It
is left up to the user to determine how to get the text address of the
loaded GRUB image.
Signed-off-by: Glenn Washburn <development@efficientek.com>
---
grub-core/gdb_grub.in | 21 ++++++++-
grub-core/gdb_helper.py.in | 87 ++++++++++++++++++++++++++++++++++++++
2 files changed, 107 insertions(+), 1 deletion(-)
diff --git a/grub-core/gdb_grub.in b/grub-core/gdb_grub.in
index fc201204de..18ce6b0eb2 100644
--- a/grub-core/gdb_grub.in
+++ b/grub-core/gdb_grub.in
@@ -1,6 +1,6 @@
###
### Load debuging information about GNU GRUB 2 modules into GDB
-### automatically. Needs readelf, Python and gdb_helper.py script
+### automatically. Needs readelf, objdump, Python and gdb_helper.py script
###
### Has to be launched from the writable and trusted
### directory containing *.image and *.module
@@ -12,6 +12,25 @@
source gdb_helper.py
+define dynamic_load_symbols
+ dynamic_load_kernel_exec_symbols $arg0
+
+ # We may have been very late to loading the kernel.exec symbols and
+ # and modules may already be loaded. So load symbols for any already
+ # loaded.
+ load_all_modules
+
+ if $is_grub_loaded()
+ runtime_load_module
+ end
+end
+document dynamic_load_symbols
+ Load debugging symbols from kernel.exec and any loaded modules given
+ the address of the .text segment of the UEFI binary in memory. Also
+ setup session to automatically load module symbols for modules loaded
+ in the future.
+end
+
define load_all_modules
set $this = grub_dl_head
while ($this != 0)
diff --git a/grub-core/gdb_helper.py.in b/grub-core/gdb_helper.py.in
index 4306ef448a..8d5ee1d292 100644
--- a/grub-core/gdb_helper.py.in
+++ b/grub-core/gdb_helper.py.in
@@ -4,6 +4,23 @@ import subprocess
##### Convenience functions #####
+class IsGrubLoaded (gdb.Function):
+ """Return 1 if GRUB has been loaded in memory, otherwise 0.
+The hueristic used is checking if the first 4 bytes of the memory pointed
+to by the _start symbol are not 0. This is true for QEMU on the first run
+of GRUB. This may not be true on physical hardware, where memory is not
+necessarily cleared on soft reset. This may not also be true in QEMU on
+soft resets. Also this many not be true when chainloading GRUB.
+"""
+
+ def __init__ (self):
+ super (IsGrubLoaded, self).__init__ ("is_grub_loaded")
+
+ def invoke (self):
+ return int (gdb.parse_and_eval ("*(int *) _start")) != 0
+
+is_grub_loaded = IsGrubLoaded ()
+
class IsUserCommand (gdb.Function):
"""Set the second argument to true value if first argument is the name
of a user-defined command.
@@ -24,6 +41,76 @@ is_user_command = IsUserCommand ()
##### Commands #####
+# Loading symbols is complicated by the fact that kernel.exec is an ELF
+# ELF binary, but the UEFI runtime is PE32+. All the data sections of
+# the ELF binary are concatenated (accounting for ELF section alignment)
+# and put into one .data section of the PE32+ runtime image. So given
+# the load address of the .data PE32+ section we can determine the
+# addresses each ELF data section maps to. The UEFI application is
+# loaded into memory just as it is laid out in the file. It is not
+# assumed that the binary is available, but it is known that the .text
+# section directly precedes the .data section and that .data is EFI
+# page aligned. Using this, the .data offset can be found from the .text
+# address.
+class GrubLoadKernelExecSymbols (gdb.Command):
+ """Load debugging symbols from kernel.exec given the address of the
+.text segment of the UEFI binary in memory."""
+
+ PE_SECTION_ALIGN = 12
+
+ def __init__ (self):
+ super (GrubLoadKernelExecSymbols, self).__init__
("dynamic_load_kernel_exec_symbols",
+ gdb.COMMAND_USER,
+ gdb.COMPLETE_EXPRESSION)
+
+ def invoke (self, arg, from_tty):
+ self.dont_repeat ()
+ args = gdb.string_to_argv (arg)
+
+ if len (args) != 1:
+ raise RuntimeError ("dynamic_load_kernel_exec_symbols expects exactly
one argument")
+
+ sections = self.parse_objdump_sections ("kernel.exec")
+ pe_text = args[0]
+ text_size = [s['size'] for s in sections if s['name'] == '.text'][0]
+ pe_data_offset = self.alignup (text_size, self.PE_SECTION_ALIGN)
+
+ sym_load_cmd_parts = ["add-symbol-file", "kernel.exec", pe_text]
+ offset = 0
+ for section in sections:
+ if 'DATA' in section["flags"] or section["name"] == ".bss":
+ offset = self.alignup (offset, section["align"])
+ sym_load_cmd_parts.extend (["-s", section["name"], "(%s+0x%x+0x%x)" %
(pe_text, pe_data_offset, offset)])
+ offset += section["size"]
+ gdb.execute (' '.join (sym_load_cmd_parts))
+
+ @staticmethod
+ def parse_objdump_sections (filename):
+ fields = ("idx", "name", "size", "vma", "lma", "fileoff", "align")
+ re_section = re.compile ("^\s*" + "\s+".join(["(?P<%s>\S+)" % f for f in
fields]))
+ c = subprocess.run (["objdump", "-h", filename], text=True,
capture_output=True)
+ section_lines = c.stdout.splitlines ()[5:]
+ sections = []
+
+ for i in range (len (section_lines) >> 1):
+ m = re_section.match (section_lines[i * 2])
+ s = dict (m.groupdict ())
+ for f in ("size", "vma", "lma", "fileoff"):
+ s[f] = int (s[f], 16)
+ s["idx"] = int (s["idx"])
+ s["align"] = int (s["align"].split ("**", 1)[1])
+ s["flags"] = section_lines[(i * 2) + 1].strip ().split (", ")
+ sections.append (s)
+ return sections
+
+ @staticmethod
+ def alignup (addr, align):
+ pad = (addr % (1 << align)) and 1 or 0
+ return ((addr >> align) + pad) << align
+
+dynamic_load_kernel_exec_symbols = GrubLoadKernelExecSymbols ()
+
+
class GrubLoadModuleSymbols (gdb.Command):
"""Load module symbols at correct locations.
Takes one argument which is a pointer to a grub_dl_t struct."""
--
2.34.1
- [PATCH v5 01/14] gdb: Fix redirection issue in dump_module_sections, (continued)
- [PATCH v5 01/14] gdb: Fix redirection issue in dump_module_sections, Glenn Washburn, 2022/12/23
- [PATCH v5 02/14] gdb: Prevent wrapping when writing to .segments.tmp, Glenn Washburn, 2022/12/23
- [PATCH v5 03/14] gdb: If no modules have been loaded, do not try to load module symbols, Glenn Washburn, 2022/12/23
- [PATCH v5 04/14] gdb: Move runtime module loading into runtime_load_module, Glenn Washburn, 2022/12/23
- [PATCH v5 05/14] gdb: Conditionally run GDB script logic for dynamically or statically positioned GRUB, Glenn Washburn, 2022/12/23
- [PATCH v5 06/14] gdb: Only connect to remote target once when first sourced, Glenn Washburn, 2022/12/23
- [PATCH v5 10/14] gdb: Allow running user-defined commands at GRUB start, Glenn Washburn, 2022/12/23
- [PATCH v5 07/14] gdb: Replace module symbol loading implementation with Python one, Glenn Washburn, 2022/12/23
- [PATCH v5 11/14] gdb: Fix issue with breakpoints defined before the GRUB image is loaded, Glenn Washburn, 2022/12/23
- [PATCH v5 12/14] gdb: Add extra early initialization symbols for i386-pc, Glenn Washburn, 2022/12/23
- [PATCH v5 08/14] gdb: Add functions to make loading from dynamically positioned targets easier,
Glenn Washburn <=
- [PATCH v5 09/14] gdb: Add more support for debugging on EFI platforms, Glenn Washburn, 2022/12/23
- [PATCH v5 13/14] gdb: Modify gdb prompt when running gdb_grub script, Glenn Washburn, 2022/12/23
- [PATCH v5 14/14] docs: Add debugging chapter to development documentation, Glenn Washburn, 2022/12/23