From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa:symtab] deprecate inside_entry_func
Date: Sat, 01 Nov 2003 02:37:00 -0000 [thread overview]
Message-ID: <3FA31C64.9060306@gnu.org> (raw)
In-Reply-To: <20031101004233.GA11987@nevyn.them.org>
> On Fri, Oct 31, 2003 at 07:07:28PM -0500, Andrew Cagney wrote:
>
>> Hello,
>>
>> This patch deprecates the function inside_entry_func. Per the new comments:
>>
>> + /* NOTE: cagney/2003-10-31: A very simple test, such as
>> + get_frame_func == entry_point should be sufficient for
>> + identifying a pc in the entry function. Does anyone know why it
>> + wasn't sufficient and hence, why the very convoluted
>> + "deprecated_inside_entry_func" is needed. */
>> + /* NOTE: cagney/2003-10-31: An ABI and its crt0 code should define
>> + and implement a clean frame termination. Not doing that is
>> + really a bug in the ABI/crt0, and, hence, not a reason for
>> + enabling the call to deprecated_inside_entry_func. */
>
>
> If handling broken systems isn't the job of GDB, then I surely don't
> know what is.
> Do you have a reason for wanting to deprecate this function?
Per my first new comment:
/* NOTE: cagney/2003-10-31: A very simple test, such as
get_frame_func == entry_point should be sufficient for
identifying a pc in the entry function. Does anyone know why it
wasn't sufficient and hence, why the very convoluted
"deprecated_inside_entry_func" is needed. */
and the previous comment:
/* NOTE: cagney/2003-02-25: Don't enable until someone has found
hard evidence that this is needed. */
There is _still_ no evidence that this disabled hack is needed - time to
deprecate it.
Andrew
next prev parent reply other threads:[~2003-11-01 2:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-01 0:07 Andrew Cagney
2003-11-01 0:37 ` Kevin Buettner
2003-11-01 0:46 ` Andrew Cagney
2003-11-01 0:55 ` Kevin Buettner
2003-11-01 2:27 ` Andrew Cagney
2003-11-07 17:31 ` Kevin Buettner
2003-11-07 21:25 ` Andrew Cagney
2003-11-01 0:42 ` Daniel Jacobowitz
2003-11-01 2:37 ` Andrew Cagney [this message]
2003-11-09 0:13 ` Daniel Jacobowitz
2003-11-09 2:40 ` Andrew Cagney
2003-11-09 3:50 ` Daniel Jacobowitz
2003-11-21 19:53 ` Andrew Cagney
2003-11-21 19:59 ` Daniel Jacobowitz
2003-11-21 20:11 ` Kevin Buettner
2003-11-21 20:46 ` Andrew Cagney
2003-11-21 20:48 ` Daniel Jacobowitz
2003-11-21 20:55 ` Andrew Cagney
2003-11-21 21:04 ` Daniel Jacobowitz
2003-11-21 21:24 ` Kevin Buettner
2003-11-21 21:54 ` Daniel Jacobowitz
2003-11-21 22:40 ` Kevin Buettner
2003-11-22 0:37 ` Andrew Cagney
2003-11-22 0:41 ` Daniel Jacobowitz
2003-11-21 20:07 ` David Carlton
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=3FA31C64.9060306@gnu.org \
--to=cagney@gnu.org \
--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