From: Kevin Buettner <kevinb@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>, Andrew Cagney <ac131313@redhat.com>
Cc: Kevin Buettner <kevinb@redhat.com>, gdb@sources.redhat.com
Subject: Re: frame_register_unwind(): "frame != NULL" assertion failure
Date: Fri, 14 Feb 2003 15:24:00 -0000 [thread overview]
Message-ID: <1030214152426.ZM10734@localhost.localdomain> (raw)
In-Reply-To: Daniel Jacobowitz <drow@mvista.com> "Re: frame_register_unwind(): "frame != NULL" assertion failure" (Feb 14, 10:14am)
On Feb 14, 10:14am, Daniel Jacobowitz wrote:
> > However, can you please first investigate modifying the start of
> > mips_init_extra_frame_info() where it does:
> >
> > proc_desc = get_next_frame (fci) ? .....
> >
> > to, when get_next_frame(fci) is null, call:
> >
> > find_proc_desc (get_frame_pc (fci), fci, 1);
> >
> > that is the current, and not prev frame.
>
> I'm pretty sure that won't work - we're initializing the saved regs for
> fci right now, and find_proc_desc wants a frame to read registers out
> of.
Yes, I agree.
next prev parent reply other threads:[~2003-02-14 15:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 21:24 Kevin Buettner
2003-02-13 21:29 ` Daniel Jacobowitz
2003-02-13 21:35 ` Kevin Buettner
2003-02-13 21:48 ` Kevin Buettner
2003-02-13 23:27 ` Kevin Buettner
2003-02-14 14:58 ` Andrew Cagney
2003-02-14 15:14 ` Daniel Jacobowitz
2003-02-14 15:24 ` Kevin Buettner [this message]
2003-02-17 15:37 ` Andrew Cagney
2003-02-17 23:21 ` Kevin Buettner
2003-02-18 2:39 ` Andrew Cagney
2003-02-18 1:59 ` Kevin Buettner
2003-02-18 22:51 ` Andrew Cagney
2003-02-20 16:18 ` Kevin Buettner
2003-02-20 16:28 ` Andrew Cagney
2003-02-20 16:36 ` Kevin Buettner
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=1030214152426.ZM10734@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=gdb@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