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/30044] Flawed logic when releasing values from all_values buffer
Date: Tue, 31 Jan 2023 18:29:14 +0000 [thread overview]
Message-ID: <bug-30044-4717-uF0HBA2H6N@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30044-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30044
--- Comment #10 from Hannes Domani <ssbssa at sourceware dot org> ---
(In reply to Tom Tromey from comment #9)
> Created attachment 14643 [details]
> patch
>
> I have a patch that seems to fix both of these.
> Can you try this?
> If it works I'll turn your crasher into a test case.
Yes, with this applied there are no more crashes.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-01-31 18:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 18:59 [Bug python/30044] New: " ssbssa at sourceware dot org
2023-01-24 19:00 ` [Bug python/30044] " ssbssa at sourceware dot org
2023-01-24 19:01 ` ssbssa at sourceware dot org
2023-01-24 19:01 ` ssbssa at sourceware dot org
2023-01-24 19:02 ` ssbssa at sourceware dot org
2023-01-24 19:02 ` ssbssa at sourceware dot org
2023-01-24 19:03 ` ssbssa at sourceware dot org
2023-01-24 19:04 ` ssbssa at sourceware dot org
2023-01-24 19:07 ` tromey at sourceware dot org
2023-01-30 22:16 ` tromey at sourceware dot org
2023-01-30 23:22 ` tromey at sourceware dot org
2023-01-31 1:46 ` tromey at sourceware dot org
2023-01-31 2:04 ` tromey at sourceware dot org
2023-01-31 18:29 ` ssbssa at sourceware dot org [this message]
2023-02-11 1:13 ` tromey at sourceware dot org
2023-02-27 22:56 ` cvs-commit at gcc dot gnu.org
2023-02-27 22:57 ` tromey at sourceware dot org
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-30044-4717-uF0HBA2H6N@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).