public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: nathan@stitt.org
To: gcc-gnats@gcc.gnu.org
Subject: c++/7188: Segfault with template class and recursive (incorrect) initalizer list.
Date: Tue, 02 Jul 2002 20:36:00 -0000	[thread overview]
Message-ID: <20020703032729.25765.qmail@sources.redhat.com> (raw)


>Number:         7188
>Category:       c++
>Synopsis:       Segfault with template class and recursive (incorrect) initalizer list.
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Jul 02 20:36:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     nathan@stitt.org
>Release:        3.1
>Organization:
>Environment:
Debian w both self compiled g++ v 3.1 and from unstable, vers. 3.1.1 20020606 (Debian prerelease)
>Description:
If a templated class is created, the initializer list is appently not checked for recursive initialization ( my guess anyway ).  Code attached should never compile, and indead doesn't under g++ 2.95 and 3.0, however 3.1 segfaults while attempting compile.  If template declaration from top of class is removed, segfault does not occur and appropriate error message is issued.

This is not a big deal to myself, as code is clearly very wrong. However since I was silly enough to accidently write it, I imagine that it's possible someone else will do the same at some point.
>How-To-Repeat:
attempt compile of attached code under g++ 3.1
>Fix:
Don't create brain dead code such as this :)
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="crash.cc"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="crash.cc"

dGVtcGxhdGUgPGNsYXNzIFQgPgpjbGFzcyBmb28gCnsKcHVibGljOgoJZm9vKCkgOiBmb28oKQoJ
ewoKCX0KfTsKCmludAptYWluKGludCBhcmdjLCBjaGFyICoqYXJndil7Cglmb288aW50PiBiOwoJ
cmV0dXJuIDE7Cn0K


             reply	other threads:[~2002-07-03  3:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-02 20:36 nathan [this message]
2002-09-14 13:45 nathan
2002-10-02 12:59 mmitchel
2002-10-02 23:57 mmitchel

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=20020703032729.25765.qmail@sources.redhat.com \
    --to=nathan@stitt.org \
    --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).