public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: snyder@fnal.gov
To: gcc-gnats@gcc.gnu.org
Subject: c++/9415: g++ 3.4: can't call base class's virtual function
Date: Thu, 23 Jan 2003 07:06:00 -0000 [thread overview]
Message-ID: <200301230700.BAA06820@d0sgibnl1.fnal.gov> (raw)
>Number: 9415
>Category: c++
>Synopsis: g++ 3.4: can't call base class's virtual function
>Confidential: no
>Severity: critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: wrong-code
>Submitter-Id: net
>Arrival-Date: Thu Jan 23 07:06:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: scott snyder
>Release: 3.4 20030121 (experimental)
>Organization:
<organization of PR author (multiple lines)>
>Environment:
System: Linux karma 2.4.19-emp_2419p5a829i #1 Tue Sep 3 17:42:17 EST 2002 i686 unknown
Architecture: i686
<machine, os, target, libraries (multiple lines)>
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../gcc/configure --prefix=/usr/local/gcc --enable-threads=posix --enable-long-long
>Description:
In the program below, the call to d0_Object::activate() does not call
the method requested. Instead, it does a virtual call to activate() ---
meaning that this program, when run, goes into an infinite recursion.
If i change it so that d0_DBObject is not a template class, then the
program behaves as expected.
$ g++ -o x x.cc
$ ./x
act
act
act
act
act
act
act
... and so on ...
>How-To-Repeat:
----------------------
extern "C" int printf (...);
struct d0_Object
{
virtual void activate() {}
};
template <class K>
struct d0_DBObject : public d0_Object
{
void activate() { printf ("act\n"); d0_Object::activate();}
};
int main ()
{
d0_DBObject<int> x;
x.activate();
return 0;
}
----------------------
>Fix:
<how to correct or work around the problem, if known (multiple lines)>
>Release-Note:
>Audit-Trail:
>Unformatted:
reply other threads:[~2003-01-23 7:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200301230700.BAA06820@d0sgibnl1.fnal.gov \
--to=snyder@fnal.gov \
--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).