public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: dave@joot.com
To: gcc-gnats@gcc.gnu.org
Subject: c++/6185: Core Dump using gcc -O3
Date: Thu, 04 Apr 2002 23:56:00 -0000	[thread overview]
Message-ID: <20020405075356.18235.qmail@sources.redhat.com> (raw)


>Number:         6185
>Category:       c++
>Synopsis:       Core Dump using gcc -O3
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Apr 04 23:56:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Dave Jarvis
>Release:        gcc v3.0.2
>Organization:
>Environment:
Linux RedHat v7.2
>Description:
Compiling the attached source at optimisation level 3
results in a core dump 100% of the time.  Regular compile,
or compiling at -O2 never core dumps.
>How-To-Repeat:
gcc -O3 filler.c
strip a.out
./a.out > file.txt
Aborted (core dumped)
>Fix:
Don't compile using -O3.  ;-)
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="filler.c"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="filler.c"

LyoKICogVXNlZCB0byBmaWxsIHVwIGEgdXNlcidzIGZ1bGwgZmlsZSBxdW90YSBpbiBhIHNpbmds
ZSBmaWxlLiAgUmVkaXJlY3QKICogdGhlIG91dHB1dCB0byBhIGZpbGUuICBFeGFtcGxlIHVzYWdl
OgogKgogKiAgIGZpbGxlciA+IGxhcmdlZmlsZS5kYXQKICoKICogRnV0dXJlIG9wdGlvbnMgbWF5
IGluY2x1ZGU6CiAqICAgLXIgICAgIC0tIE91dHB1dCByYW5kb20gY2hhcmFjdGVycwogKiAgIC1j
ICMjIyAtLSBTcGVjaWZ5IEFTQ0lJIHZhbHVlIG9mIGNoYXJhY3RlciB0byB1c2UgKDAgLSAyNTUp
CiAqLwoKI2luY2x1ZGUgPHN0ZGlvLmg+CgojaW5jbHVkZSA8dWxpbWl0Lmg+CiNpbmNsdWRlIDx1
bmlzdGQuaD4KCi8qIEhvdyBtYW55IGNoYXJhY3RlcnMgYXJlIHRvIGJlIHdyaXR0ZW4gYXQgb25l
IHRpbWU/CiAqLwojZGVmaW5lIEJVRkZFUl9TSVpFICgxNjM4NCkKCi8qIFdoYXQgY2hhcmFjdGVy
IGlzIHRvIGJlIHVzZWQgZm9yIHdyaXRpbmc/CiAqLwojZGVmaW5lIEJVRkZFUl9GSUxMICgyNTUp
CgppbnQgbWFpbiggdm9pZCApCnsKICBjaGFyIGJ1ZmZlclsgQlVGRkVSX1NJWkUgXTsKICBsb25n
IGkgPSBCVUZGRVJfU0laRSAtIDE7CgogIC8qIEluaXRpYWxpemUgdGhlIGJ1ZmZlci4KICAgKi8K
ICB3aGlsZSggaS0tICkKICAgIGJ1ZmZlcltpXSA9IEJVRkZFUl9GSUxMOwoKICAvKiBOVUxMIHRl
cm1pbmF0ZSBmb3IgZnByaW50Zi4KICAgKi8KICBidWZmZXJbIEJVRkZFUl9TSVpFIC0gMSBdID0g
MDsKCiAgaSA9IChsb25nKXVsaW1pdCggVUxfR0VURlNJWkUsIDAgKSAqIChsb25nKTUxMjsKCiAg
LyogV3JpdGUgdGhlIGJ1ZmZlcidzIHRvIHN0YW5kYXJkIG91dHB1dC4KICAgKi8KICB3aGlsZSgg
aS0tICkKICAgIGZwcmludGYoIHN0ZG91dCwgIiVzIiwgYnVmZmVyICk7CgogIHJldHVybiAwOwp9
Cgo=


             reply	other threads:[~2002-04-05  7:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-04 23:56 dave [this message]
2002-04-06 16:07 rodrigc

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=20020405075356.18235.qmail@sources.redhat.com \
    --to=dave@joot.com \
    --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).