public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "ssbssa at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug exp/28980] GDB crashes when using GDB/MI and python pretty printers in some cases
Date: Sat, 19 Mar 2022 13:09:54 +0000 [thread overview]
Message-ID: <bug-28980-4717-yWXOUmFQhr@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28980-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28980
Hannes Domani <ssbssa at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |12.1
--- Comment #1 from Hannes Domani <ssbssa at sourceware dot org> ---
Can be easily reproduced with python when copying an optimized-out value:
(gdb) py print(gdb.Value(gdb.Value(5).type.optimized_out()))
C:/src/repos/binutils-gdb.git/gdb/value.c:1731: internal-error: value*
value_copy(value*): Assertion `arg->contents != nullptr' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) n
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-03-19 13:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-19 13:06 [Bug exp/28980] New: " ssbssa at sourceware dot org
2022-03-19 13:09 ` ssbssa at sourceware dot org [this message]
2022-03-19 13:10 ` [Bug exp/28980] " ssbssa at sourceware dot org
2022-03-22 13:37 ` jan at vrany dot io
2022-04-06 20:11 ` cvs-commit at gcc dot gnu.org
2022-04-06 21:02 ` cvs-commit at gcc dot gnu.org
2022-04-06 21:02 ` 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-28980-4717-yWXOUmFQhr@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).