From: Richard Earnshaw <rearnsha@arm.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: Richard.Earnshaw@arm.com, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] ARM: Eliminate EXTRA_FRAME_INFO & FRAME_FIND_SAVED_REGS
Date: Mon, 14 Jan 2002 02:18:00 -0000 [thread overview]
Message-ID: <200201141018.KAA21380@cam-mail2.cambridge.arm.com> (raw)
In-Reply-To: Your message of "Sun, 13 Jan 2002 10:24:26 MST." <1020113172426.ZM25643@localhost.localdomain>
> > 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().
>
Argh! I even looked for this and couldn't find it :-( I suspect because
patch hasn't set the function signature correctly for the hunk....
@@ -2209,6 +2225,10 @@ The valid values are:\n");
add_com ("othernames", class_obscure, arm_othernames,
"Switch to the next set of register names.");
+
+ /* Allocate extra_info and saved_regs fields in the 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?
Doh! right again.
OK. I withdraw my version in favour of yours. All we need to do now is
get someone to approve it.
R.
next prev parent reply other threads:[~2002-01-14 10:18 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
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 [this message]
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=200201141018.KAA21380@cam-mail2.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@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