This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/10944] Assertion `get_frame_type (frame) == DUMMY_FRAME'failed
- From: "tschwinge at sourceware dot org" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Sun, 12 Aug 2012 10:35:59 +0000
- Subject: [Bug gdb/10944] Assertion `get_frame_type (frame) == DUMMY_FRAME'failed
- Auto-submitted: auto-generated
- References: <bug-10944-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=10944
--- Comment #6 from Thomas Schwinge <tschwinge at sourceware dot org> 2012-08-12 10:35:59 UTC ---
Is this a multi-core/hardware-multi-threaded system? And where is the
dummy frame's return breakpoint set? I have seen and fixed this issue on
another (unpublished) GDB port where the dummy call's return breakpoint
was the entry point at address 0, and another hardware-thread would hit
that one, which thusly confused GDB. Moving the dummy call's return onto
the thread's stack was the solution, by adding a push_dummy_code function
and Âset_gdbarch_call_dummy_location (gdbarch, ON_STACK);Â.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.