public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/29449] Crash on load when the target does not support shared libraries
Date: Mon, 08 Aug 2022 16:06:49 +0000 [thread overview]
Message-ID: <bug-29449-4717-Jb5i9FVUyX@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29449-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29449
--- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom Tromey <tromey@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=ce81f9d6fa885a3faa41613debc8771304dc469b
commit ce81f9d6fa885a3faa41613debc8771304dc469b
Author: Tom Tromey <tromey@adacore.com>
Date: Mon Aug 8 09:56:47 2022 -0600
Fix regression from gdbarch registry change
The gdbarch registry patch introduced a regression that could cause a
crash when opening files in gdb. The bug is that, previously, the
solib ops would default to current_target_so_ops; but the patch
changed this code to default to nullptr. This patch fixes the bug by
reintroducing the earlier behavior. This is PR gdb/29449.
I managed to reproduce the bug with a riscv-elf build and then
verified that this fixes the problem.
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=29449
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-08-08 16:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 16:19 [Bug gdb/29449] New: Crash on load when there's no shared library support research_trasio at irq dot a4lg.com
2022-08-05 16:20 ` [Bug gdb/29449] " research_trasio at irq dot a4lg.com
2022-08-05 16:32 ` research_trasio at irq dot a4lg.com
2022-08-07 5:39 ` [Bug gdb/29449] Crash on load when the target does not support shared libraries research_trasio at irq dot a4lg.com
2022-08-08 14:33 ` tromey at sourceware dot org
2022-08-08 15:13 ` tromey at sourceware dot org
2022-08-08 16:02 ` tromey at sourceware dot org
2022-08-08 16:06 ` cvs-commit at gcc dot gnu.org [this message]
2022-08-08 16:07 ` tromey at sourceware dot org
2022-08-09 2:36 ` research_trasio at irq dot a4lg.com
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-29449-4717-Jb5i9FVUyX@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).