Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jiong Wang <jiong.wang@foss.arm.com>
To: GDB <gdb-patches@sourceware.org>
Subject: [AArch64][5/6] Implement gdbarch_core_read_description
Date: Wed, 09 Aug 2017 12:18:00 -0000	[thread overview]
Message-ID: <acf76d2e-3d27-434d-b144-c8c61ea5cd5f@foss.arm.com> (raw)
In-Reply-To: <c8484136-c4f2-cda2-6a0d-f8293b111cdd@foss.arm.com>

[-- Attachment #1: Type: text/plain, Size: 528 bytes --]

Currently, AArch64 only have one target description which is tdesc_aarch64.  So,
we haven't implemented any target description detetion mechanism for core file.

This patch is an initial implement of core_read_description method.  The "pauth"
feature or any future feature can use this to conditionally return selected
description.

gdb/
2017-08-09  Jiong Wang<jiong.wang@arm.com>

	* aarch64-linux-tdep.c (aarch64_linux_core_read_description): New
	function.
	(aarch64_linux_init_abi): Register gdbarch_core_read_description.


[-- Attachment #2: gdb-5.patch --]
[-- Type: text/x-patch, Size: 1116 bytes --]

diff --git a/gdb/aarch64-linux-tdep.c b/gdb/aarch64-linux-tdep.c
index d2ca70a..ec6125a 100644
--- a/gdb/aarch64-linux-tdep.c
+++ b/gdb/aarch64-linux-tdep.c
@@ -231,6 +231,20 @@ aarch64_linux_iterate_over_regset_sections (struct gdbarch *gdbarch,
       NULL, cb_data);
 }
 
+/* Determine target description from core file.  */
+
+static const struct target_desc *
+aarch64_linux_core_read_description (struct gdbarch *gdbarch,
+				     struct target_ops *target, bfd *abfd)
+{
+  CORE_ADDR aarch64_hwcap = 0;
+
+  if (target_auxv_search (target, AT_HWCAP, &aarch64_hwcap) != 1)
+    return NULL;
+
+  return tdesc_aarch64;
+}
+
 /* Implementation of `gdbarch_stap_is_single_operand', as defined in
    gdbarch.h.  */
 
@@ -1018,6 +1032,8 @@ aarch64_linux_init_abi (struct gdbarch_info info, struct gdbarch *gdbarch)
 
   set_gdbarch_iterate_over_regset_sections
     (gdbarch, aarch64_linux_iterate_over_regset_sections);
+  set_gdbarch_core_read_description
+    (gdbarch, aarch64_linux_core_read_description);
 
   /* SystemTap related.  */
   set_gdbarch_stap_integer_prefixes (gdbarch, stap_integer_prefixes);

  parent reply	other threads:[~2017-08-09 12:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <c8484136-c4f2-cda2-6a0d-f8293b111cdd@foss.arm.com>
2017-08-09 12:17 ` [AArch64][3/6] DWARF unwinder support for signed return address Jiong Wang
2017-08-10 11:08   ` Pedro Alves
2017-08-10 13:35     ` Jiong Wang
2017-08-09 12:18 ` Jiong Wang [this message]
2017-08-09 14:22   ` [AArch64][5/6] Implement gdbarch_core_read_description Yao Qi
2017-08-09 14:57     ` Jiong Wang
2017-08-09 15:43       ` Jiong Wang
2017-08-09 16:04         ` Yao Qi
2017-08-09 16:40           ` Jiong Wang
2017-08-09 12:18 ` [AArch64][4/6] Prologue scan unwinder support for signed return address Jiong Wang

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=acf76d2e-3d27-434d-b144-c8c61ea5cd5f@foss.arm.com \
    --to=jiong.wang@foss.arm.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