This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug c++/22708] New: GDB internal-error : skip_inline_frames : Assertion `find_inline_frame_state (ptid) == NULL' failed.
- From: "prakash_prasad at yahoo dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Sun, 14 Jan 2018 15:04:55 +0000
- Subject: [Bug c++/22708] New: GDB internal-error : skip_inline_frames : Assertion `find_inline_frame_state (ptid) == NULL' failed.
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=22708
Bug ID: 22708
Summary: GDB internal-error : skip_inline_frames : Assertion
`find_inline_frame_state (ptid) == NULL' failed.
Product: gdb
Version: 7.9
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: c++
Assignee: unassigned at sourceware dot org
Reporter: prakash_prasad at yahoo dot com
Target Milestone: ---
gdb coreprg
break filename:linenum
Breakpoint 1, reached
(gdb) set pagination off
(gdb) set logging on
Copying output to gdb.txt.
(gdb) while 1
>step
>end
.....
132 else if(!ReleaseSemaphore(((SemaphoreStruct*)handle)->NULL,NULL,
NULL)) // this is application code
../../../../src/gdb-7.9.1/gdb/inline-frame.c:338: internal-error:
skip_inline_frames: Assertion `find_inline_frame_state (ptid) == NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) [answered Y; input not from terminal]
This is a bug, please report it. For instructions, see:
<http://www.gnu.org/software/gdb/bugs/>.
../../../../src/gdb-7.9.1/gdb/inline-frame.c:338: internal-error:
skip_inline_frames: Assertion `find_inline_frame_state (ptid) == NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) [answered Y; input not from terminal]
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
--
You are receiving this mail because:
You are on the CC list for the bug.