From: Kevin Buettner <kevinb@redhat.com>
To: Kinsey Moore <kinsey.moore@oarcorp.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb: Add support for TLS under RTEMS
Date: Thu, 23 Apr 2026 18:54:18 -0700 [thread overview]
Message-ID: <20260423185418.2d28545c@f42-zbm-amd> (raw)
In-Reply-To: <20260422151840.661343-1-kinsey.moore@oarcorp.com>
On Wed, 22 Apr 2026 10:18:40 -0500
Kinsey Moore <kinsey.moore@oarcorp.com> wrote:
> This support uses the presence of the ".rtemsroset" section to detect
> whether an ELF was created using RTEMS. This works for current RTEMS
> development (7) branch, 6 branch, 5 branch, and 4.11 branch. This
> registers the TLS callback for architectures under which RTEMS is known
> to support TLS. The RTEMS self-hosted GDB server is only expected to
> support TLS in RTEMS 6 branch and the current development branch and
> will only respond without error to qGetTLSAddr request in those
> versions. Other GDB servers will respond with TLS information if
> available.
[...]
> diff --git a/gdb/configure.tgt b/gdb/configure.tgt
> index ba418653e86..05160714069 100644
> --- a/gdb/configure.tgt
> +++ b/gdb/configure.tgt
> @@ -128,6 +128,8 @@ case "${targ}" in
> os_obs="netbsd-tdep.o solib-svr4.o";;
> *-*-openbsd*)
> os_obs="obsd-tdep.o solib-svr4.o";;
> +*-rtems*)
> + os_obs="rtems-tdep.o solib-svr4.o";;
> esac
[...]
> +#include "solib-svr4.h"
[...]
> +static void
> +rtems_init_abi (struct gdbarch_info info, struct gdbarch *gdbarch)
> +{
> + set_gdbarch_fetch_tls_load_module_address (gdbarch,
> +
> svr4_fetch_objfile_link_map); +}
Does (or will) RTEMS have SVR4 shared library support? If not, then
the various references to solib-svr4 files and mechanisms should
be removed.
Kevin
next prev parent reply other threads:[~2026-04-24 1:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-22 15:18 Kinsey Moore
2026-04-24 1:54 ` Kevin Buettner [this message]
2026-04-28 15:43 ` Tom Tromey
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=20260423185418.2d28545c@f42-zbm-amd \
--to=kevinb@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=kinsey.moore@oarcorp.com \
/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