From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>, Michal Ludvig <mludvig@suse.cz>
Cc: GDB Patches <gdb-patches@sources.redhat.com>
Subject: Re: [RFA] Artifical dwarf2 debug info
Date: Thu, 02 Jan 2003 20:54:00 -0000 [thread overview]
Message-ID: <3E14A709.9040902@redhat.com> (raw)
In-Reply-To: <20021218153733.GA11738@nevyn.them.org>
fde = get_fde_for_addr (context->ra - 1);
> >+
> >+ if (fde == NULL)
> >+ fde = guess_generic_fde (context->ra - 1);
> >
> > if (fde == NULL)
> > return;
Just to be clear. The above is the change that I think is wrong.
Instead of this function `guessing' the source of the FDE, the code
needs to be re-structured so that the caller always supplies a
pre-created FDE.
That way a dwarf2 cfi frame can call the above function with an FDE
built from the object files debug info, while an artifical frame can
call it with an artifically created FDE. There is no guessing involved.
--
This is part of a long standing problem - it predates dwarf2cf by many
years. Instead of using recursion, people modify debug/target dependent
frame code so that it attempts to directly handle all cases. Cf all the
PC_IN_CALL_DUMMY(frame->next), PC_IN_SIGTRAMP(frame->next) and other
tests scattered through out the -tdep.c code; and the calls to
get_next_frame() in dwarf2cfi.c.
Andrew
next prev parent reply other threads:[~2003-01-02 20:54 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-14 17:31 Michal Ludvig
2002-12-14 22:53 ` Eli Zaretskii
2002-12-15 11:03 ` Daniel Jacobowitz
2002-12-16 7:28 ` Michal Ludvig
2002-12-16 7:49 ` Daniel Jacobowitz
2002-12-16 9:27 ` Michal Ludvig
2002-12-16 9:54 ` Daniel Jacobowitz
2002-12-16 10:38 ` Eli Zaretskii
2002-12-20 8:43 ` Michal Ludvig
2002-12-20 10:51 ` Eli Zaretskii
2002-12-16 9:25 ` Andrew Cagney
2002-12-16 9:40 ` Daniel Jacobowitz
2002-12-16 10:04 ` Andrew Cagney
2002-12-16 10:17 ` Daniel Jacobowitz
2002-12-16 10:56 ` Andrew Cagney
2002-12-16 11:13 ` Daniel Jacobowitz
2002-12-16 11:34 ` Andrew Cagney
2002-12-16 11:57 ` Daniel Jacobowitz
2002-12-16 12:10 ` Andrew Cagney
2002-12-16 12:42 ` Daniel Jacobowitz
2002-12-17 6:23 ` Michal Ludvig
2002-12-17 6:28 ` Andrew Cagney
2002-12-17 8:42 ` Daniel Jacobowitz
2002-12-18 4:39 ` Andrew Cagney
2002-12-18 10:05 ` Daniel Jacobowitz
2003-01-02 20:54 ` Andrew Cagney [this message]
2003-01-02 21:19 ` Daniel Jacobowitz
2003-01-02 23:05 ` Andrew Cagney
2003-01-02 23:27 ` Daniel Jacobowitz
2003-01-03 0:28 ` Andrew Cagney
2002-12-16 9:46 ` Michal Ludvig
2002-12-16 9:57 ` Andrew Cagney
2002-12-16 10:01 ` Michal Ludvig
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=3E14A709.9040902@redhat.com \
--to=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mludvig@suse.cz \
/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