This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug guile/17923] scheme exception about invalid object in a backtrace
- From: "mdaniels at lanl dot gov" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Sat, 07 Feb 2015 17:56:28 +0000
- Subject: [Bug guile/17923] scheme exception about invalid object in a backtrace
- Auto-submitted: auto-generated
- References: <bug-17923-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17923
--- Comment #6 from Marcus Daniels <mdaniels at lanl dot gov> ---
"for the frame problem, is it possible to set a breakpoint on one of the frame
functions early on, when f_smob->inferior is not NULL, set a watchpoint on it,
and then continue? When the watchpoint triggers a backtrace may be sufficient
to isolate the culprit."
Could you clarify if there is ever a situation in which f_smob->inferior ought
to become NULL, even if the debugged program is continuing?
For now I'm trying to add guards to frame-* calls using the modified
frame-valid to see what other problems I run into. If it is an endless chain
of problems, I can't afford to keep debugging and need to take another
approach. If it is a bounded set, then perhaps I can afford to debug these
issues.
--
You are receiving this mail because:
You are on the CC list for the bug.