From: Kevin Buettner <kevinb@redhat.com>
To: Richard.Earnshaw@arm.com
Cc: Kevin Buettner <kevinb@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] ARM: Eliminate EXTRA_FRAME_INFO & FRAME_FIND_SAVED_REGS
Date: Sun, 13 Jan 2002 09:32:00 -0000 [thread overview]
Message-ID: <1020113172426.ZM25643@localhost.localdomain> (raw)
In-Reply-To: Richard Earnshaw <rearnsha@arm.com> "Re: [PATCH] ARM: Eliminate EXTRA_FRAME_INFO & FRAME_FIND_SAVED_REGS" (Jan 13, 3:28pm)
On Jan 13, 3:28pm, Richard Earnshaw wrote:
> > On Jan 12, 11:50am, Richard Earnshaw wrote:
> >
> > > This patch eliminates the deprecated macros EXTRA_FRAME_INFO &
> > > FRAME_FIND_SAVED_REGS from the arm target support files and replaces them
> > > with the new methods for doing this.
> >
> > I submitted a patch to do this last month. Unfortunately, the ARM
> > maintainers have not had a chance to review it yet.
> >
> > See http://sources.redhat.com/ml/gdb-patches/2001-12/msg00397.html
[...]
> Hmm, it seems substantially the same as mine, but with a couple of minor
> differences.
>
> 1) You don't seem to initialize the pointer fields in the static frame
> structure "prologue_cache".
My patch does this allocation in _initialize_arm_tdep() whereas yours
does it in check_prologue_cache() and save_prologue_cache().
> 2) Similarly you don't seem to be allocating the saved_regs for the
> caller_fi frame (arm_frame_chain). You do, however, allocate the
> extra_info.
> 3) You have a cleanup for the extra_info allocated above, which I hadn't
> thought about. I think one is also needed for the saved_regs.
Are you sure? Here are what I believe to be the relevant lines from
the arm_frame_chain hunk:
+ caller_fi.saved_regs = (CORE_ADDR *) xcalloc (1, SIZEOF_FRAME_SAVED_REGS);
+ old_chain = make_cleanup (xfree, caller_fi.saved_regs);
+ caller_fi.extra_info = xcalloc (1, sizeof (struct frame_extra_info));
+ make_cleanup (xfree, caller_fi.extra_info);
saved_regs is being allocated and a cleanup is being created. Were you
perhaps refering to some other hunk?
Kevin
next prev parent reply other threads:[~2002-01-13 17:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 5:39 [PATCH] fix inferior_pid argument for arm-netbsd Richard Earnshaw
[not found] ` <rearnsha@arm.com>
2002-01-09 7:40 ` Kevin Buettner
2002-01-09 7:54 ` Richard Earnshaw
2002-01-10 9:59 ` Richard Earnshaw
2002-01-10 10:38 ` Kevin Buettner
2002-01-12 9:47 ` [PATCH] ARM: Eliminate EXTRA_FRAME_INFO & FRAME_FIND_SAVED_REGS Kevin Buettner
2002-01-13 7:28 ` Richard Earnshaw
2002-01-13 9:32 ` Kevin Buettner [this message]
2002-01-13 10:40 ` Andrew Cagney
2002-01-13 11:08 ` Andrew Cagney
2002-01-13 11:48 ` Kevin Buettner
2002-01-13 11:54 ` Andrew Cagney
2002-01-14 2:18 ` Richard Earnshaw
2002-01-12 3:51 Richard Earnshaw
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=1020113172426.ZM25643@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=Richard.Earnshaw@arm.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