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 python/12127] gdb with python support still get crash on showing uninitialized local variables
Date: Sun, 10 Dec 2023 10:16:26 +0000 [thread overview]
Message-ID: <bug-12127-4717-5di3ZTg4A6@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12127-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=12127
Hannes Domani <ssbssa at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|NEW |RESOLVED
--- Comment #11 from Hannes Domani <ssbssa at sourceware dot org> ---
Fixed some time ago.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2023-12-10 10:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-16 1:13 [Bug gdb/12127] New: " asmwarrior at gmail dot com
2012-02-07 20:59 ` [Bug python/12127] " tromey at redhat dot com
2012-03-03 14:01 ` asmwarrior at gmail dot com
2012-03-03 14:02 ` asmwarrior at gmail dot com
2012-06-02 6:53 ` xunxun1982 at gmail dot com
2013-05-07 5:08 ` asmwarrior at gmail dot com
2013-05-07 5:09 ` asmwarrior at gmail dot com
2013-05-07 6:01 ` asmwarrior at gmail dot com
2013-05-07 6:16 ` asmwarrior at gmail dot com
2013-11-24 7:31 ` asmwarrior at gmail dot com
2013-12-19 16:29 ` xdje42 at gmail dot com
2014-02-16 19:43 ` jackie.rosen at hushmail dot com
2014-05-28 19:43 ` schwab at sourceware dot org
2023-12-09 12:55 ` ssbssa at sourceware dot org
2023-12-10 6:11 ` asmwarrior at gmail dot com
2023-12-10 10:16 ` ssbssa at sourceware dot org [this message]
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-12127-4717-5di3ZTg4A6@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).