Exception handling & Purify

Exception handling & Purify

[Marc Dionne]

I presume that this is likely to be a Purify issue (since the code runs
fine on its own), but I was wondering if anyone here would have any
insight.

Attempts to run this bit of code:

#include <iostream>
int main(int argc, char *argv[])
{
    try
    {
        throw(1);
    }
    catch (int &i)
    {
        cout << "I caught an int." << endl;
    }
    cout << "Exiting." << endl;
    return 0;
}

under Purify results in a core dump with the following messages:

      Purify instrumented ./t (pid 11461 at Thu Jun 17 09:06:00 1999)
      ABR: Array bounds read
      ABR: Array bounds read
      ABR: Array bounds read
      ABR: Array bounds read
      MSE: Memory segment error
      COR: Fatal core dump

It runs fine on its own.  This is consistent with any egcs version, and
any gcc 2.8.* version, but works ok with gcc 2.7.2.  Is Purify known not
to play nice with this type of code?

Thanks,
Marc

Re: Exception handling & Purify

[Martin v. Loewis]

> I presume that this is likely to be a Purify issue (since the code
> runs fine on its own), but I was wondering if anyone here would have
> any insight.

You didn't mention what platform you are using. Purify has big
problems with gcc >= 2.8 on many platforms, in particular with dwarf
exception handling.

Rational is beta-testing a purify version that supports the most
recent gcc right now, and it fixes a lot of problems. You'll probably
have to contact Rational for details.

There is also a problem with non-pic code, I suggest to link
statically in case you've been using shared library. This is true in
particular for libstdc++.

Regards,
Martin

Re: Exception handling & Purify

[Martin v. Loewis]

> I presume that this is likely to be a Purify issue (since the code
> runs fine on its own), but I was wondering if anyone here would have
> any insight.

You didn't mention what platform you are using. Purify has big
problems with gcc >= 2.8 on many platforms, in particular with dwarf
exception handling.

Rational is beta-testing a purify version that supports the most
recent gcc right now, and it fixes a lot of problems. You'll probably
have to contact Rational for details.

There is also a problem with non-pic code, I suggest to link
statically in case you've been using shared library. This is true in
particular for libstdc++.

Regards,
Martin

Exception handling & Purify

[Marc Dionne]

I presume that this is likely to be a Purify issue (since the code runs
fine on its own), but I was wondering if anyone here would have any
insight.

Attempts to run this bit of code:

#include <iostream>
int main(int argc, char *argv[])
{
    try
    {
        throw(1);
    }
    catch (int &i)
    {
        cout << "I caught an int." << endl;
    }
    cout << "Exiting." << endl;
    return 0;
}

under Purify results in a core dump with the following messages:

      Purify instrumented ./t (pid 11461 at Thu Jun 17 09:06:00 1999)
      ABR: Array bounds read
      ABR: Array bounds read
      ABR: Array bounds read
      ABR: Array bounds read
      MSE: Memory segment error
      COR: Fatal core dump

It runs fine on its own.  This is consistent with any egcs version, and
any gcc 2.8.* version, but works ok with gcc 2.7.2.  Is Purify known not
to play nice with this type of code?

Thanks,
Marc