public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "seth.pellegrino at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug backtrace/29395] blockframe.c:79: internal-error: get_frame_block: Assertion `bl != NULL' failed.
Date: Thu, 15 Dec 2022 18:08:51 +0000 [thread overview]
Message-ID: <bug-29395-4717-EnodGrqcG2@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29395-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29395
Seth Pellegrino <seth.pellegrino at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |seth.pellegrino at gmail dot com
--- Comment #1 from Seth Pellegrino <seth.pellegrino at gmail dot com> ---
I'm seeing the same assertion failure with booth 12.1 and the latest master
(38665d717a3) when attaching to a corefile: immediately after starting up gdb,
trying `bt` will yield the assertion failure. `maint set dwarf unwinders off`
followed by `bt` does not crash, but doesn't yield much of a backtrace either.
The core file (1.1GB) + binary + debug symbols (combined, 2.6GB) can be found
here: https://f004.backblazeb2.com/file/shared-sethp/gdb-29395.tar.zstd (total
compressed size: 1.2GB).
I also threw in the core dumps from gdb itself, both from 12.1
(core.gdb.1000.d4a79394d6ce443f8e9e6308ab0afc23.216854.1671119608000000.zst)
and master
(core.gdb.1000.d4a79394d6ce443f8e9e6308ab0afc23.383687.1671123437000000.zst)
because compressed they're only 65MB each (though they do both decompress to
~600MB).
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-12-15 18:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 13:02 [Bug backtrace/29395] New: " georgepee at gmail dot com
2022-07-25 15:27 ` [Bug backtrace/29395] " georgepee at gmail dot com
2022-08-24 13:20 ` georgepee at gmail dot com
2022-12-15 18:08 ` seth.pellegrino at gmail dot com [this message]
2022-12-15 18:11 ` simon.marchi at polymtl dot ca
2022-12-15 18:43 ` seth.pellegrino at gmail dot com
2022-12-15 19:14 ` simon.marchi at polymtl dot ca
2022-12-15 20:09 ` simon.marchi at polymtl dot ca
2022-12-15 20:27 ` simon.marchi at polymtl dot ca
2022-12-15 21:02 ` seth.pellegrino at gmail dot com
2022-12-15 21:12 ` simon.marchi at polymtl dot ca
2022-12-16 16:27 ` tromey at sourceware dot org
2022-12-20 23:03 ` simark at simark dot ca
2022-12-21 4:49 ` simark at simark dot ca
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=bug-29395-4717-EnodGrqcG2@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).