From: Corinna Vinschen <vinschen@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Remove calls to inside_entry_file
Date: Thu, 10 Apr 2003 11:12:00 -0000 [thread overview]
Message-ID: <20030410111230.GO1928@cygbert.vinschen.de> (raw)
In-Reply-To: <3E8EE0A6.4070403@redhat.com>
On Sat, Apr 05, 2003 at 08:56:54AM -0500, Andrew Cagney wrote:
> Consider that approved.
Thanks, applied.
Corinna
2003-04-10 Corinna Vinschen <vinschen@redhat.com>
* blockframe.c (legacy_frame_chain_valid): Move call to
DEPRECATED_FRAME_CHAIN_VALID before calls to inside_entry_func and
inside_entry_file.
Index: blockframe.c
===================================================================
RCS file: /cvs/src/src/gdb/blockframe.c,v
retrieving revision 1.67
diff -u -p -r1.67 blockframe.c
--- blockframe.c 6 Apr 2003 18:36:22 -0000 1.67
+++ blockframe.c 10 Apr 2003 11:09:32 -0000
@@ -575,6 +575,11 @@ legacy_frame_chain_valid (CORE_ADDR fp,
if (INNER_THAN (fp, get_frame_base (fi)))
return 0;
+ /* If the architecture has a custom DEPRECATED_FRAME_CHAIN_VALID,
+ call it now. */
+ if (DEPRECATED_FRAME_CHAIN_VALID_P ())
+ return DEPRECATED_FRAME_CHAIN_VALID (fp, fi);
+
/* If we're already inside the entry function for the main objfile, then it
isn't valid. */
if (inside_entry_func (get_frame_pc (fi)))
@@ -586,11 +591,6 @@ legacy_frame_chain_valid (CORE_ADDR fp,
dbxread) figure out which object is the entry file is somewhat hokey. */
if (inside_entry_file (frame_pc_unwind (fi)))
return 0;
-
- /* If the architecture has a custom DEPRECATED_FRAME_CHAIN_VALID,
- call it now. */
- if (DEPRECATED_FRAME_CHAIN_VALID_P ())
- return DEPRECATED_FRAME_CHAIN_VALID (fp, fi);
return 1;
}
--
Corinna Vinschen
Cygwin Developer
Red Hat, Inc.
mailto:vinschen@redhat.com
next prev parent reply other threads:[~2003-04-10 11:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-27 11:33 Corinna Vinschen
2003-03-29 0:28 ` Andrew Cagney
2003-04-01 15:31 ` Corinna Vinschen
2003-04-01 15:38 ` Corinna Vinschen
2003-04-01 15:39 ` Andrew Cagney
2003-04-01 16:18 ` Corinna Vinschen
2003-04-01 16:35 ` Andrew Cagney
2003-04-01 17:03 ` Corinna Vinschen
2003-04-01 17:30 ` Andrew Cagney
2003-04-01 19:58 ` Daniel Jacobowitz
2003-04-02 9:27 ` Corinna Vinschen
2003-04-02 16:36 ` Andrew Cagney
2003-04-02 16:42 ` Daniel Jacobowitz
2003-04-02 17:03 ` Andrew Cagney
2003-04-02 17:05 ` Daniel Jacobowitz
2003-04-02 18:20 ` Andrew Cagney
2003-04-02 18:23 ` Daniel Jacobowitz
2003-04-02 20:11 ` Andrew Cagney
2003-04-02 20:38 ` Daniel Jacobowitz
2003-04-03 13:17 ` Corinna Vinschen
2003-04-05 13:57 ` Andrew Cagney
2003-04-10 11:12 ` Corinna Vinschen [this message]
2003-04-02 16:39 ` Daniel Jacobowitz
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=20030410111230.GO1928@cygbert.vinschen.de \
--to=vinschen@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