From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: GDB Patches <gdb-patches@sources.redhat.com>
Subject: Re: [patch/rfc] Add a sentinel frame
Date: Wed, 19 Feb 2003 17:11:00 -0000 [thread overview]
Message-ID: <3E53BBCB.2010003@redhat.com> (raw)
In-Reply-To: <20030219165623.GA7961@nevyn.them.org>
>> No. GDB is trying to perform:
>>
>> pop_frame (get_current_frame())
>>
>> with the assumption that it has a dummy frame and get_current_frame()
>> will return it.
>>
>
>> >That's what happens on i386 IIRC...
>
>
> I thought that we wouldn't reach frame_chain_valid if the next frame
> was a dummy frame. Hmm, that only seems to happen for deprecated
> generic dummy frames:
The variable `use_generic_dummy_frames' is deprecated because it is
redundant. All targets should use generic dummy frames. Yes, the
variable name is screwed up :-(
> if (DEPRECATED_USE_GENERIC_DUMMY_FRAMES
> && DEPRECATED_PC_IN_CALL_DUMMY (get_frame_pc (fi), 0, 0))
> return 1;
> Oh I didn't realize the contents of frame_chain_valid had ended up
> repeated in get_prev_frame, I've been looking at the wrong function.
> That's why I didn't understand you. Should the check above exist in
> get_prev_frame also?
When you first committed that stuff, I warned you that would happen :-)
The above test handled differently.
> [Why does this logic need to be in more than one place?]
Because frame_chain_valid() is only there to keep legacy code working.
Need to rename it, need to deprecate the rest of those old methods.
Andrew
next prev parent reply other threads:[~2003-02-19 17:11 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-23 20:54 Andrew Cagney
2003-01-27 21:42 ` Andrew Cagney
2003-02-10 23:36 ` Michal Ludvig
2003-02-11 16:48 ` Andrew Cagney
2003-02-18 11:21 ` Michal Ludvig
2003-02-19 13:27 ` Andrew Cagney
2003-02-19 14:04 ` Daniel Jacobowitz
2003-02-19 16:46 ` Andrew Cagney
2003-02-19 16:56 ` Daniel Jacobowitz
2003-02-19 17:11 ` Andrew Cagney [this message]
2003-02-19 17:17 ` Daniel Jacobowitz
2003-02-19 17:46 ` Andrew Cagney
2003-02-19 17:56 ` Daniel Jacobowitz
2003-02-19 18:36 ` Andrew Cagney
2003-02-19 18:52 ` Daniel Jacobowitz
2003-02-19 20:22 ` Andrew Cagney
2003-02-19 20:39 ` Daniel Jacobowitz
2003-02-19 21:21 ` Andrew Cagney
2003-02-20 19:32 ` Daniel Jacobowitz
2003-02-19 21:45 ` Andrew Cagney
2003-02-20 19:32 ` Daniel Jacobowitz
2003-02-25 16:24 ` Michal Ludvig
2003-02-25 19:43 ` Andrew Cagney
2003-02-25 21:00 ` Michal Ludvig
2003-02-25 21:12 ` Andrew Cagney
2003-02-26 8:04 ` Michal Ludvig
2003-02-27 18:27 ` Andrew Cagney
2003-02-28 13:02 ` Michal Ludvig
2003-02-28 15:48 ` Andrew Cagney
2003-03-05 17:38 ` Michal Ludvig
2003-03-05 18:25 ` Andrew Cagney
2003-03-06 16:00 ` Michal Ludvig
2003-03-06 20:13 ` Andrew Cagney
2003-03-06 22:42 ` [RFA] Dummy frames on x86-64 Michal Ludvig
2003-03-07 14:50 ` Andrew Cagney
2003-02-25 22:41 ` [patch/rfc] Add a sentinel frame Andrew Cagney
2003-02-25 21:21 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=3E53BBCB.2010003@redhat.com \
--to=ac131313@redhat.com \
--cc=drow@mvista.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