Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Kris Warkentin" <kewarken@qnx.com>
To: "Elena Zannoni" <ezannoni@redhat.com>
Cc: <gdb-patches@sources.redhat.com>
Subject: Re: [Patch] fix for PR:1291
Date: Wed, 24 Sep 2003 01:20:00 -0000	[thread overview]
Message-ID: <002601c3823a$209cd910$6400a8c0@dash> (raw)
In-Reply-To: <16240.46973.557418.422147@localhost.redhat.com>

> kewarken writes:
>  > Credit to inaba@src.ricoh.co.jp for his original find and patch and to
>  > Colin Burgess for noting the differences between gcc 2 and 3.
>  >
>  > ChangeLog:
>  >
>  > 2003-09-16  Kris Warkentin  <kewarken@qnx.com>
>  >
>  > * sh-tdep.c: Properly detect frame prologues for functions with
>  > more than 256 bytes of local variables.
>
> You should give credit to these folks in the changelog entry.

Certainly.

> I wonder if this can be captured in a test case?  How does your change
> interacts with Corinna's rewrite?

I'll take a look at it when I have some more time next week.  The test case
is very simple so I can easily check to see if Corinna's stuff fixes it.
Unfortunately my available gdb cycles have been extremely low lately since
we have a lot of critical internal stuff that I've been grabbed for.

cheers,

Kris


  reply	other threads:[~2003-09-24  1:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-16 18:48 kewarken
2003-09-23 21:03 ` Elena Zannoni
2003-09-24  1:20   ` Kris Warkentin [this message]
2003-10-16 18:46     ` [Patch] fix for PR:1291 (Ping Corinna) Kris Warkentin
2003-10-24 13:16       ` Elena Zannoni
2003-10-24 14:27         ` Kris Warkentin
2003-10-24 14:39           ` Elena Zannoni
2003-09-23 21:25 [Patch] fix for PR:1291 Michael Elizabeth Chastain

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='002601c3823a$209cd910$6400a8c0@dash' \
    --to=kewarken@qnx.com \
    --cc=ezannoni@redhat.com \
    --cc=gdb-patches@sources.redhat.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