Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] More dynamic allocation of scratch `struct frame_info'
Date: Mon, 06 Jan 2003 21:52:00 -0000	[thread overview]
Message-ID: <3E19FA50.8030001@redhat.com> (raw)
In-Reply-To: <3E185137.4010807@redhat.com>

> I need to check that this hasn't broken the arm so I'll commit it once that is done (in a few days).

Done.  No regressions.  Committed.

Andrew

> 2003-01-05  Andrew Cagney  <ac131313@redhat.com>
> 
> 	* frame.h (deprecated_frame_xmalloc_with_cleanup): Declare.
> 	* frame.c (deprecated_frame_xmalloc_with_cleanup): New function.
> 	* arm-tdep.c (arm_frame_chain): Allocate caller_fi using
> 	deprecated_frame_xmalloc_with_cleanup.
> 	* m32r-tdep.c (m32r_virtual_frame_pointer): Allocate `fi' using
> 	deprecated_frame_xmalloc.
> 	* mcore-tdep.c (analyze_dummy_frame): Ditto for dummy.
> 	* mn10200-tdep.c (mn10200_frame_chain): Ditto for dummy_frame.
> 



      reply	other threads:[~2003-01-06 21:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-05 15:37 Andrew Cagney
2003-01-06 21:52 ` Andrew Cagney [this message]

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=3E19FA50.8030001@redhat.com \
    --to=ac131313@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