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 21:02:12 +0000	[thread overview]
Message-ID: <bug-29395-4717-5kUx5BpNNR@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29395-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29395

--- Comment #7 from Seth Pellegrino <seth.pellegrino at gmail dot com> ---
(In reply to Simon Marchi from comment #5)
> Ok, I got it to crash by installing the Arch Linux packages you provided on
> Arch Linux system, and then:
> 
> $ /usr/bin/gdb /usr/bin/kicad -c kicad-core-gdb-crasher
> 
> I then tried using my own build of GDB, it wouldn't crash.  I rebuilt the
> Arch package with debug info to understand where it crashes, it's within a
> frame-filter implementation.  To reproduce the crash, we need this to be
> loaded:
> 
> [ ... ]

Oh, interesting: so it's something particular about the way the arch package is
built? Is that frame-filter something I can turn off to avoid the crash for
now?

> 
> PS: I think you'll find the master branch of GDB (to be GDB 13) much faster
> to initially load the debug info, thanks to Tom Tromey's DWARF reader
> refactor.  I can really see the difference with binaries of this size,
> between 12 and master.

Oh neat! I'll have to check that out: I've definitely been feeling the time it
takes to load the debug info loading so far.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-12-15 21:02 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
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 [this message]
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-5kUx5BpNNR@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).