From: Daniel Jacobowitz <drow@mvista.com>
To: Jafa <jafa@silicondust.com>
Cc: gdb@sources.redhat.com
Subject: Re: kickstaring frame handling
Date: Tue, 01 Jul 2003 22:56:00 -0000 [thread overview]
Message-ID: <20030701225642.GA16116@nevyn.them.org> (raw)
In-Reply-To: <0a1201c3400e$9754e930$0a02a8c0@scenix.com>
On Tue, Jul 01, 2003 at 01:22:50PM -0700, Jafa wrote:
> Hi guys,
>
> How does the new frame handling get kickstarted (ie create the currently
> executing frame)?
>
> The ip2k port is dying with the message "internal-error: deprecated_read_fp"
> triggered from legacy_get_prev_frame, called from unwind_to_current_frame.
>
> Obviously it should not be trying to call this function so I must have
> missed something.
>
> I will keep tracing through it but if the problem is obvious to anyone then
> it would save some debug time.
See legacy_frame_p. You can't provide the legacy methods and use the
new code.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2003-07-01 22:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-01 20:25 Jafa
2003-07-01 22:56 ` Daniel Jacobowitz [this message]
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=20030701225642.GA16116@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=jafa@silicondust.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).