This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug gdb/17611] malloc failure shouldn't be flagged as an internal error


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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]