This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
c++/10048: Compiler doesn't catch failure to return a value - causes crashing code
- From: cjc at cs dot brown dot edu
- To: gcc-gnats at gcc dot gnu dot org
- Date: 12 Mar 2003 20:29:53 -0000
- Subject: c++/10048: Compiler doesn't catch failure to return a value - causes crashing code
- Reply-to: cjc at cs dot brown dot edu
>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=