From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Add frame_is_callee_p(), use in dwarf2-frame.c?
Date: Thu, 03 Jul 2003 16:18:00 -0000 [thread overview]
Message-ID: <3F04573F.8050803@redhat.com> (raw)
In-Reply-To: <20030702193625.GA10838@nevyn.them.org>
> On Wed, Jul 02, 2003 at 03:28:50PM -0400, Andrew Cagney wrote:
>
>> >Regardless, for a ``normal frame'' test, I'd like to suggest
>
>> >>``frame_is_callee_p()'' as something suitable descriptive. Thoughts?
>
>> >
>> >
>> >You've leapt ahead of me again. What would frame_is_callee_p mean?
>
>>
>> The frame is a callee, it has a caller with a call instruction?
>
>
> Oh, makes sense to me.
But if you can think of a better name :-)
The flip side would be to try something like ``frame is interrupt'' or
`frame unwind is correct'', but then that gets into refinements like
``frame might be correct because of decr pc after break'' ....
Andrew
next prev parent reply other threads:[~2003-07-03 16:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-02 18:47 Andrew Cagney
2003-07-02 19:12 ` Daniel Jacobowitz
2003-07-02 19:28 ` Andrew Cagney
2003-07-02 19:36 ` Daniel Jacobowitz
2003-07-03 16:18 ` Andrew Cagney [this message]
2003-07-02 19:14 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=3F04573F.8050803@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