Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Cc: Richard Earnshaw <Richard.Earnshaw@arm.com>,
		Shaun Jackman <sjackman@gmail.com>
Subject: RFC: Use the ARM CPSR as a fallback to determine ARM/Thumb
Date: Mon, 20 Feb 2006 22:03:00 -0000	[thread overview]
Message-ID: <20060220214918.GA28798@nevyn.them.org> (raw)

I'm fishing for comments on this change.  In arm_pc_is_thumb, if we can not
find a symbol covering the supplied PC, we assume ARM mode; it seems that it
would be strictly more useful to assume the current mode.

This patch _should not be used_ as is!  Paul Brook cleverly noticed that
this will mess up breakpoint_from_pc when removing breakpoints, causing us
to insert 2-byte breakpoints and remove 4-byte ones across a mode switch.
I'm going to have to mess with the target_remove_breakpoint interface
to fix that, so I wanted to get opinions on this patch first before I dig
in.

This is still a somewhat creepy thing to do.  You can find quotes of me in
the gdb@ list archives saying that this is "the way to madness".  However,
I've been debugging some code which jumps to Thumb-mode routines in ROM
today, and my GDB doesn't yet have symbol information for the ROM code; so
I'm well down the way to madness without this patch, and it's somewhat
better with.

Maybe there should be a "set" option for the default when no symbol is
found, allowing the user to throttle this back to ARM-only if that works
better for them?

-- 
Daniel Jacobowitz
CodeSourcery

2006-02-20  Daniel Jacobowitz  <dan@codesourcery.com>

	* arm-tdep.c (arm_pc_is_thumb): Fall back to the CPSR.

NOTE: NOT FOR COMMIT

Index: src/gdb/arm-tdep.c
===================================================================
--- src.orig/gdb/arm-tdep.c	2006-02-02 15:38:35.000000000 -0500
+++ src/gdb/arm-tdep.c	2006-02-20 16:11:02.000000000 -0500
@@ -184,13 +184,15 @@ arm_pc_is_thumb (CORE_ADDR memaddr)
   /* Thumb functions have a "special" bit set in minimal symbols.  */
   sym = lookup_minimal_symbol_by_pc (memaddr);
   if (sym)
-    {
-      return (MSYMBOL_IS_SPECIAL (sym));
-    }
-  else
-    {
-      return 0;
-    }
+    return (MSYMBOL_IS_SPECIAL (sym));
+
+  /* If we couldn't find any symbol, but we're talking to a running
+     target, then trust the current value of $cpsr.  */
+  if (target_has_registers)
+    return (read_register (ARM_PS_REGNUM) & 0x20) != 0;
+
+  /* Otherwise we're out of luck; we assume ARM.  */
+  return 0;
 }
 
 /* Remove useless bits from addresses in a running program.  */


             reply	other threads:[~2006-02-20 21:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-20 22:03 Daniel Jacobowitz [this message]
2006-02-21 15:36 ` Richard Earnshaw
2006-02-21 16:10   ` Daniel Jacobowitz
2006-03-02 22:23     ` Daniel Jacobowitz
2006-03-02 22:52       ` Mark Kettenis
2006-03-02 23:02         ` Daniel Jacobowitz
2006-03-02 23:10           ` Mark Kettenis
2006-03-02 23:23             ` Daniel Jacobowitz
2008-05-01 18:38       ` Daniel Jacobowitz
2008-05-02 10:17         ` Eli Zaretskii
2008-05-02 14:06           ` Daniel Jacobowitz
2008-05-02 15:47             ` Eli Zaretskii
2008-05-02 16:03               ` Daniel Jacobowitz
2008-05-02 20:34                 ` Eli Zaretskii
2006-02-25 11:12 ` Jim Blandy
2006-02-26 13:10   ` Daniel Jacobowitz

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=20060220214918.GA28798@nevyn.them.org \
    --to=drow@false.org \
    --cc=Richard.Earnshaw@arm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sjackman@gmail.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