public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: cjc@cs.brown.edu
To: gcc-gnats@gcc.gnu.org
Subject: c++/10048: Compiler doesn't catch failure to return a value - causes crashing code
Date: Wed, 12 Mar 2003 20:36:00 -0000	[thread overview]
Message-ID: <20030312202953.5104.qmail@sources.redhat.com> (raw)


>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=


             reply	other threads:[~2003-03-12 20:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-12 20:36 cjc [this message]
2003-03-12 21:28 bangerth
2003-03-12 21:36 Christian Convey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030312202953.5104.qmail@sources.redhat.com \
    --to=cjc@cs.brown.edu \
    --cc=gcc-gnats@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).