From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] frv-tdep.c: Stop backtraces in entry func, not entry file
Date: Thu, 16 Oct 2003 04:10:00 -0000 [thread overview]
Message-ID: <20031016041055.GA3565@nevyn.them.org> (raw)
In-Reply-To: <1031016033144.ZM24591@localhost.localdomain>
On Wed, Oct 15, 2003 at 08:31:45PM -0700, Kevin Buettner wrote:
> Yes, I agree that deprecated_inside_entry_file() is a bad idea. I
> suspect it was being used because past and existing
> implementations of inside_entry_func() proved to be unreliable.
FYI, I have some local hacks for the dwarf2 reader that are needed to
use inside_entry_func reliably (or a number of other things...) in the
presence of discarded sections. I'll try to remember to post them but
the gist is that until the linker does better, we need to detect
wildly-inaccurate bounds on DIEs and not adjust the compilation unit's
bounds (or the start function's, either).
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-10-16 4:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-14 20:51 Kevin Buettner
2003-10-14 21:55 ` Andrew Cagney
2003-10-15 22:39 ` Michael Snyder
2003-10-16 0:07 ` Kevin Buettner
2003-10-16 1:15 ` Andrew Cagney
2003-10-16 3:31 ` Kevin Buettner
2003-10-16 4:10 ` Daniel Jacobowitz [this message]
2003-10-20 23:57 ` Andrew Cagney
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=20031016041055.GA3565@nevyn.them.org \
--to=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