This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/19394] New: crash in get_frame_type() while stepping (s)
- From: "gerhard.gappmeier at ascolab dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Tue, 22 Dec 2015 12:41:46 +0000
- Subject: [Bug gdb/19394] New: crash in get_frame_type() while stepping (s)
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=19394
Bug ID: 19394
Summary: crash in get_frame_type() while stepping (s)
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: gerhard.gappmeier at ascolab dot com
Target Milestone: ---
Overview:
This problem is somehow related to having a custom pretty printer installed.
When debugging an application and using the step command to step into a
specific function it crashes.
I don't see anything from the pretty printer in the callstack, but without the
pretty printer it does not happen.
How to reproduce:
1.) start gdb: gdb ./server1
2.) set breakpoint on problematic function call
3.) run
3.) step -> core dumped
This happens with various GDB versions:
* GNU gdb (Gentoo 7.9.1 vanilla) 7.9.1
* Latest git version built from source
(6d265cb4a956310d2cae231ac63a37e11fe376e1)
I attached to coredump created with the latest Git build (-O1 -ggdb)
The frame info in get_frame_type is invalid for any reason:
(gdb) print *frame
$1 = {
level = 0,
pspace = 0x0,
aspace = 0x650000006c,
prologue_cache = 0x5400000072,
unwind = 0x7000000079,
...
(gdb) print *frame->unwind
Cannot access memory at address 0x7000000079
--
You are receiving this mail because:
You are on the CC list for the bug.