From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-prs-return-30998-listarch-gcc-prs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 482 invoked by alias); 12 Mar 2003 20:36:01 -0000
Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc-prs/>
List-Post: <mailto:gcc-prs@gcc.gnu.org>
List-Help: <mailto:gcc-prs-help@gcc.gnu.org>
Sender: gcc-prs-owner@gcc.gnu.org
Received: (qmail 440 invoked by uid 71); 12 Mar 2003 20:36:00 -0000
Resent-Date: 12 Mar 2003 20:36:00 -0000
Resent-Message-ID: <20030312203600.438.qmail@sources.redhat.com>
Resent-From: gcc-gnats@gcc.gnu.org (GNATS Filer)
Resent-Cc: gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org
Resent-Reply-To: gcc-gnats@gcc.gnu.org, cjc@cs.brown.edu
Received: (qmail 5106 invoked by uid 48); 12 Mar 2003 20:29:53 -0000
Message-Id: <20030312202953.5104.qmail@sources.redhat.com>
Date: Wed, 12 Mar 2003 20:36:00 -0000
From: cjc@cs.brown.edu
Reply-To: cjc@cs.brown.edu
To: gcc-gnats@gcc.gnu.org
X-Send-Pr-Version: gnatsweb-2.9.3 (1.1.1.1.2.31)
Subject: c++/10048: Compiler doesn't catch failure to return a value - causes crashing code
X-SW-Source: 2003-03/txt/msg00728.txt.bz2
List-Id: <gcc-prs.sourceware.org>


>Number:         10048
>Category:       c++
>Synopsis:       Compiler doesn't catch failure to return a value - causes crashing code
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          accepts-illegal
>Submitter-Id:   net
>Arrival-Date:   Wed Mar 12 20:36:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Christian Convey
>Release:        3.2.2
>Organization:
>Environment:
Interim Debian Linux build. Base kernel = 2.4.18
Athlon XP 1800+, 512 MB ram

gcc 3.2.2, built with:
--enable-shared --enable-threads --enable-long-long
Thread model: posix
>Description:
The code I've attached compiles without any complaint.

g++ x.C; a.out


However, if it's run unmodified, I get a crash.

I believe the error is that the compiler is willing to compile this code. Note that it does notice the code's problem when -Wall is used.
>How-To-Repeat:
Compile the code and run it.
>Fix:
Manually ensure that each function has a return statement for every path, or compile with -Wall.

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: text/x-csrc; name="x.C"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="x.C"

I2luY2x1ZGUgPHZlY3Rvcj4KI2luY2x1ZGUgPHN0cmluZz4KI2luY2x1ZGUgPGlvc3RyZWFtPgoK
dXNpbmcgbmFtZXNwYWNlIHN0ZDsKCnZlY3RvcjxzdHJpbmc+IGZvbygpCnsKfQoKaW50IG1haW4o
KQp7CiAgY291dCA8PCBmb28oKS5zaXplKCkgPDwgZW5kbDsKICByZXR1cm4gMDsKfQo=