public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "gbenson at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/17611] malloc failure shouldn't be flagged as an internal error
Date: Tue, 18 Nov 2014 15:28:00 -0000	[thread overview]
Message-ID: <bug-17611-4717-kTWQil4fyD@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17611-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=17611

Gary Benson <gbenson at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gbenson at redhat dot com

--- Comment #5 from Gary Benson <gbenson at redhat dot com> ---
I noticed this while I was refactoring the error code, but then forgot to
follow it up.  I wondered if GDB avoided using regular error to avoid trying to
throw nested exceptions if the exception throwing code then itself ran out of
memory.

GDB and gdbserver have different malloc_failure implementations.  Whatever
solution is chosen it would be good to have a single malloc_failure in
common/errors.c.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2014-11-18 15:28 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 [this message]
2024-04-11  7:57 ` vries at gcc dot gnu.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-17611-4717-kTWQil4fyD@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).