Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: GDB Patches <gdb-patches@sourceware.org>
Cc: Sergio Durigan Junior <sergiodj@redhat.com>
Subject: [PATCH 07/17] Cris support
Date: Mon, 01 Jul 2013 07:43:00 -0000	[thread overview]
Message-ID: <1372664545-3947-8-git-send-email-sergiodj@redhat.com> (raw)
In-Reply-To: <1372664545-3947-1-git-send-email-sergiodj@redhat.com>

Cris target support.  Trivial, since it shares the signal numbers with
x86.

2013-07-01  Sergio Durigan Junior  <sergiodj@redhat.com>

	* cris-tdep.c: Include linux-tdep.h.
	(cris_gdbarch_init): Set gdbarch_gdb_signal_to_target to
	linux_gdb_signal_to_target.
---
 gdb/cris-tdep.c | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/gdb/cris-tdep.c b/gdb/cris-tdep.c
index 03041e4..1d78ded 100644
--- a/gdb/cris-tdep.c
+++ b/gdb/cris-tdep.c
@@ -44,6 +44,7 @@
 #include "solib-svr4.h"
 #include "gdb_string.h"
 #include "dis-asm.h"
+#include "linux-tdep.h"
 
 enum cris_num_regs
 {
@@ -4178,7 +4179,9 @@ cris_gdbarch_init (struct gdbarch_info info, struct gdbarch_list *arches)
 
   set_solib_svr4_fetch_link_map_offsets
     (gdbarch, svr4_ilp32_fetch_link_map_offsets);
-  
+
+  set_gdbarch_gdb_signal_to_target (gdbarch, linux_gdb_signal_to_target);
+
   /* FIXME: cagney/2003-08-27: It should be possible to select a CRIS
      disassembler, even when there is no BFD.  Does something like
      "gdb; target remote; disassmeble *0x123" work?  */
-- 
1.7.11.7


  reply	other threads:[~2013-07-01  7:43 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-01  7:43 [PATCH 00/17] Implement gdbarch_gdb_signal_to_target Sergio Durigan Junior
2013-07-01  7:43 ` Sergio Durigan Junior [this message]
2013-07-01  7:43 ` [PATCH 16/17] Xtensa support Sergio Durigan Junior
2013-07-01  7:43 ` [PATCH 04/17] x86_64 support Sergio Durigan Junior
2013-07-17 17:16   ` Tom Tromey
2013-07-17 19:00     ` Mark Kettenis
2013-07-17 19:11     ` Sergio Durigan Junior
2013-07-01  7:43 ` [PATCH 06/17] AVR support Sergio Durigan Junior
2013-07-01  7:43 ` [PATCH 03/17] Alpha support Sergio Durigan Junior
2013-07-01  7:43 ` [PATCH 17/17] MIPS support Sergio Durigan Junior
2013-07-17 17:59   ` Tom Tromey
2013-07-25  6:20     ` Sergio Durigan Junior
2013-07-29 20:15       ` Pedro Alves
2013-07-01  7:43 ` [PATCH 12/17] m68klinux support Sergio Durigan Junior
2013-07-01  7:43 ` [PATCH 01/17] Implement the gdbarch.{sh,c,h} bits Sergio Durigan Junior
2013-07-01  7:43 ` [PATCH 08/17] h8300 support Sergio Durigan Junior
2013-07-01  7:43 ` [PATCH 15/17] SPARC support Sergio Durigan Junior
2013-07-01  7:43 ` [PATCH 09/17] i386 support Sergio Durigan Junior
2013-07-01  7:43 ` [PATCH 13/17] mn10300 support Sergio Durigan Junior
2013-07-01  7:43 ` [PATCH 14/17] s390 support Sergio Durigan Junior
2013-07-01  7:43 ` [PATCH 11/17] m32r support Sergio Durigan Junior
2013-07-01  7:43 ` [PATCH 10/17] IA-64 support Sergio Durigan Junior
2013-07-01  7:43 ` [PATCH 02/17] Linux kernel generic support Sergio Durigan Junior
2013-07-01 10:57   ` Sergio Durigan Junior
2013-07-01  7:43 ` [PATCH 05/17] ARM support Sergio Durigan Junior
2013-07-17 17:20   ` Tom Tromey
2013-07-25  6:25     ` Sergio Durigan Junior
2013-07-01  8:43 ` [PATCH 00/17] Implement gdbarch_gdb_signal_to_target Andreas Schwab
2013-07-01 10:40   ` Sergio Durigan Junior
2013-07-01 10:44     ` Pedro Alves
2013-07-01 10:59       ` Sergio Durigan Junior
2013-07-01 10:46 ` [PATCH 18/18] AArch64 support Sergio Durigan Junior
2013-07-08 23:08 ` [ping][PATCH 00/17] Implement gdbarch_gdb_signal_to_target Sergio Durigan Junior
2013-07-17 18:02 ` [PATCH " 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=1372664545-3947-8-git-send-email-sergiodj@redhat.com \
    --to=sergiodj@redhat.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