Article View: gnu.g++.bug
Article #889Re: new int[0]
From: Chip Salzenberg
Date: Thu, 03 Sep 1992 15:36
Date: Thu, 03 Sep 1992 15:36
11 lines
1021 bytes
1021 bytes
According to basti@orthogo.UUCP: >I just reinstalled gcc-2.2.2 on our RS6000 (configured rs6000-ibm-aix) and >stumbled again over this damn bug within __builtin_new of libgcc2.c: >Allocating e.g., new int[0], fires the new_handler! You're fixing the wrong thing. Instead of allowing malloc() to return NULL without complaint, you should say "p = malloc (sz ? sz : 1)". -- Chip Salzenberg at Teltronics/TCT <chip@tct.com>, <73717.366@compuserve.com> "Do Rush place weird subliminal backmasked messages in their songs to compel unwilling geeks to commit evil .sig atrocities?" -- Dean Engelhardt
Technical Details
Message-ID:
<m0mQJEU-0000XAC@tct.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!cis.ohio-state.edu!tct.COM!chipReferences:
<9208271421.AA07068@orthogo.uucp>Show Full Headers
Complete Article Headers
Newsgroups: gnu.g++.bug Path: arc1-ca.pugleaf.net!sparky!uunet!cis.ohio-state.edu!tct.COM!chip From: chip@tct.COM (Chip Salzenberg) Subject: Re: new int[0] Message-ID: <m0mQJEU-0000XAC@tct.com> Sender: gnulists@ai.mit.edu Organization: TC Telemanagement, Clearwater, FL References: <9208271421.AA07068@orthogo.uucp> Distribution: gnu Date: Thu, 3 Sep 1992 15:36:00 GMT Approved: bug-g++@prep.ai.mit.edu Lines: 12