From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830

Description of problem:
In the "top-level" scope of a destructor for some class B a local object of
class A will have its destructor called even if it was never initialized by its
constructor due to a return statement appearing before the declaration of the
local object.

The problem does not occur if the local object and the earlier return statement
is placed in and ordinary method. Also the problem disappears if the entire
destructor body of B is put within an otherwise redundant scope, similarly if
only the declaration of the local object is put into a new scope.

The problem also does not occur with GCC-2.96.

The problem obviously results in core dumps unless one of the mentioned
work-arounds are applied. But this is close to impossible when porting large
applications from earlier versions of gcc.

(I'm utterly amazed about the fact that RedHad has managed to release its RedHat
8.0 entirely base on gcc3.2, when gcc3.2 has susch a lethal bug within it)

Btw. it took me 3 days of reducing 50000 lines of code to around 20 before I was
even close to realizing what the bug was.

Go fix it :-)


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
$ g++ test.C
$ ./a.out

And "test.C" is:

#include <iostream>

struct A
{
  A()  { std::cerr << "c\n"; }
  ~A() { std::cerr << "d\n"; }
};

struct B
{
  ~B()
  {
    if(true) return;
    A a;
  }
};

int main()
{
  B b;
  return 0;
}


Actual Results:  I get the following output:

d

Expected Results:  I should have had no output:


Additional info:

The problem occurs on:
RedHat 8.0 (Full install) on dual Intel Pentium III
And various other hardware configs. with RedHat 8.0
gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7)

I would be damned if this bug does not cause segfaults and other nasty behaviour
in some applications shipped with RedHat 8.0 that use
the lethal construct.