public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/17611] malloc failure shouldn't be flagged as an internal error
Date: Thu, 11 Apr 2024 07:57:14 +0000 [thread overview]
Message-ID: <bug-17611-4717-NbHvbEBq77@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17611-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17611
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vries at gcc dot gnu.org
--- Comment #6 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Sergio Durigan Junior from comment #3)
> FWIW, the patch has been submitted upstream on 2010:
>
> <https://sourceware.org/ml/gdb-patches/2010-06/msg00005.html>
>
> But it has been rejected.
And to follow up on that, it has been removed in fedora (showing rawhide
commit):
...
commit c79314bd920e4f412d31f647ab8f4bfa79fd112d
Author: Sergio Durigan Junior <sergiodj@redhat.com>
Date: Tue Jul 2 18:30:05 2019 -0400
Rebase to FSF GDB 8.3.50.20190702 (8.4pre).
Remove gdb-bz568248-oom-is-error.patch.
...
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2024-04-11 7:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 16:06 [Bug gdb/17611] New: " xdje42 at gmail dot com
2014-11-17 19:57 ` [Bug gdb/17611] " jan.kratochvil at redhat dot com
2014-11-17 22:54 ` dje at google dot com
2014-11-17 23:30 ` sergiodj at redhat dot com
2014-11-17 23:33 ` dje at google dot com
2014-11-18 15:28 ` gbenson at redhat dot com
2024-04-11 7:57 ` vries at gcc dot gnu.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-17611-4717-NbHvbEBq77@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).