Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Meador Inge <meadori@codesourcery.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/1] ARM: Change prologue analyzer to always fallback on SP.
Date: Tue, 25 Oct 2011 02:19:00 -0000	[thread overview]
Message-ID: <4EA609CF.5010304@codesourcery.com> (raw)
In-Reply-To: <CAN9gPaGzYX42iciU0oV0pUWb5Mk=EVAjuQk2y+JpC0fHjTBTuQ@mail.gmail.com>

On 07/19/2011 03:30 PM, Daniel Jacobowitz wrote:

> On Tue, Jul 19, 2011 at 2:43 PM, Meador Inge <meadori@codesourcery.com> wrote:
>> 2011-07-19  Meador Inge  <meadori@codesourcery.com>
>>
>>        * arm-tdep.c (thumb_analyze_prologue): Always fallback on the SP
>>        register when the frame can't be determined.
>>        * arm-tdep.c (arm_analyze_prologue): Ditto.
>>
>> 2011-07-19  Meador Inge  <meadori@codesourcery.com>
>>
>>        * gdb.arch/thumb-prologue.c (switch_stack_to_same): New test function.
>>        (switch_stack_to_other): New test function.
>>        * gdb.arch/thumb-prologue.exp: New test cases.
> 
> This looks OK to me.

Thanks.  I just now got my FSF copyright assignment worked
out (on file as "William Meador Inge").  Could someone please
commit this for me?  The same patch still applies.

-- 
Meador Inge
CodeSourcery / Mentor Embedded
http://www.mentor.com/embedded-software


  reply	other threads:[~2011-10-25  0:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-19 19:05 [PATCH 0/1] ARM: Fix crash when frame cannot be found Meador Inge
2011-07-19 19:11 ` [PATCH 1/1] ARM: Change prologue analyzer to always fallback on SP Meador Inge
2011-07-19 21:04   ` Daniel Jacobowitz
2011-10-25  2:19     ` Meador Inge [this message]
2011-11-09  0:54       ` Meador Inge

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=4EA609CF.5010304@codesourcery.com \
    --to=meadori@codesourcery.com \
    --cc=drow@false.org \
    --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