From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-320808-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 17171 invoked by alias); 6 Jun 2010 13:40:31 -0000
Received: (qmail 17139 invoked by uid 48); 6 Jun 2010 13:40:21 -0000
Date: Sun, 06 Jun 2010 13:40:00 -0000
Subject: [Bug c/44435]  New: gengtype: don't test undefined value after vasprintf failure
X-Bugzilla-Reason: CC
Message-ID: <bug-44435-838@http.gcc.gnu.org/bugzilla/>
Reply-To: gcc-bugzilla@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org
From: "jim at meyering dot net" <gcc-bugzilla@gcc.gnu.org>
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2010-06/txt/msg00643.txt.bz2

Harmless, but distracting...
This is present is the latest sources on trunk.

gengtype: don't test undefined value after vasprintf failure
While libiberty's asprintf function does guarantee that the pointer is
set to NULL upon asprintf failure, POSIX/glibc make no such guarantee.
* gengtype.c (xasprintf): Don't test an undefined value upon
vasprintf failure.
* gengtype.c (oprintf): Likewise.

Patch attached.


-- 
           Summary: gengtype: don't test undefined value after vasprintf
                    failure
           Product: gcc
           Version: 4.6.0
            Status: UNCONFIRMED
          Severity: minor
          Priority: P3
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: jim at meyering dot net


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44435