From: Eli Zaretskii <eliz@gnu.org>
To: gdb@sourceware.org
Subject: Re: Building GDB 7.10 with Python support
Date: Sat, 10 Oct 2015 07:09:00 -0000 [thread overview]
Message-ID: <83h9lztd2k.fsf@gnu.org> (raw)
In-Reply-To: <20151009215602.GA15880@thewrittenword.com>
> Date: Fri, 9 Oct 2015 16:56:03 -0500
> From: Albert Chin <gdb@mlists.thewrittenword.com>
>
> (gdb) break main
> Breakpoint 1 at 0x4004c8: file d.c, line 57.
> (gdb) r
> Starting program: /opt/src/latest/devel/gdb-7.10/a.out
> A Unwinder should return gdb.UnwindInfo instance.
> findvar.c:290: internal-error: value_of_register_lazy: Assertion `frame_id_p (get_frame_id (frame))' failed.
> A problem internal to GDB has been detected,
> further debugging may prove unreliable.
> Quit this debugging session? (y or n) n
>
> Any ideas where I can start looking?
I'd start where the error message points you, i.e. in findvar.c at
line 290, where you had the assertion violation. It looks like
get_frame_id failed, so you'd probably need to step with a debugger
into that function and see what's going on there.
prev parent reply other threads:[~2015-10-10 7:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-09 21:56 Albert Chin
2015-10-10 7:09 ` Eli Zaretskii [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=83h9lztd2k.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sourceware.org \
/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