From: Luis Machado via Gdb <gdb@sourceware.org>
To: Max Larsson <max.larsson@gmx.de>, gdb@sourceware.org
Subject: Re: Porting GDB to an architecture with a shared memory model
Date: Mon, 29 Jul 2024 08:36:44 +0100 [thread overview]
Message-ID: <66e2e4cb-03ce-4cb6-b0ca-6bf8c3af3f79@arm.com> (raw)
In-Reply-To: <CAGKMySXjBTc1DZ9Eo9wNgMaHNLYxU5ZLA+Tb0YMgtCJiMXHSTQ@mail.gmail.com>
On 7/28/24 18:33, Max Larsson via Gdb wrote:
> Hi everyone,
>
> I porting or better trying to report GDB to the AmigaOS 4 PPC target (elf
> based).
> I already succeeded in (re)porting the binutils stuff, but I'm stuck with
> GDB.
>
> I have a working nat, which can create an inferior, set breakpoints,etc..
> but
> because the target has a shared memory model, the inferior is not accessible
> at the vma addresses as specified in the elf format. Currently I'm trying
> to translate
> the vma addresses used by the gdb core to the physical address where the
> inferior
> ist loaded.
>
> I found in the source the method "set_gdbarch_has_shared_address_space" and
I think the gdbarch_has_shared_address_space gets used to tell gdb to reuse the
address space rather than creating a new one, which is a step in the right direction.
> "exec_set_action_address", with which I think I could tell the gdb core
exec_set_section_address I suppose? That seems to get used in some places still,
which is good.
I think objfile_relocate is something that should be used here (maybe indirectly through
some other means), maybe alongside some information about where in memory things were
loaded for your case. But I can't see a way for you to directly influence the way is works.
> where the inferior
> is loaded, so that I don't need to translate the address, but until know I
> wasn't
> able to use them correctly.
>
> So can someone give me a hint how to realize that, or how gdb support such
> a target,
> or not?
I can tell gdb supports/used to support uclinux, but I'm not sure about the
state of such support currently.
Maybe set_objfile_default_section_offset, which eventually calls objfile_relocate
could provide hints on how you could change gdb's view of the memory positioning.
Also, check gdb/tic6x-linux-tdep.c and how it relocates things through a solib
layer (gdb/solib-dsbt.c I think). For instance, dsbt_relocate_main_executable.
next prev parent reply other threads:[~2024-07-29 7:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-28 17:33 Max Larsson via Gdb
2024-07-29 7:36 ` Luis Machado via Gdb [this message]
2024-08-05 6:26 ` Max Larsson via Gdb
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=66e2e4cb-03ce-4cb6-b0ca-6bf8c3af3f79@arm.com \
--to=gdb@sourceware.org \
--cc=luis.machado@arm.com \
--cc=max.larsson@gmx.de \
/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