Re: __cxa_atexit and "FAIL: cxxtest run"

[Ranjit Mathew <rmathew at gmail dot com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ranjit Mathew wrote:
>   As I indicated in an earlier message, I have started seeing
> a "FAIL: cxxtest run" in the libjava testsuite on GCC mainline
> in recent times (a week, or two at the most). This testcase
> can be found in "$GCC_SRC/libjava/testsuite/libjava.jni".

[...]

> The difference is that I use "--enable-__cxa_atexit" for
> configuring GCC while the others don't. I prefer to use
> this option, the system GCC provided by Red Hat uses it
> and according to:

FWIW, this looks somewhat similar to PR libstdc++/23591:

  http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23591

It looks like libstdc++.so.6 was unloaded a bit too
prematurely for the exit handlers and xdr_u_long_internal()
is just a red herring for the real problem.

How can I verify this theory? That is, how can I verify
that libstdc++.so has really been unloaded at the time
of the fault and how can I see what really ought to have
been mapped at that address?

Since --enable-__cxa_atexit is used by almost all
distributions (but not for some reason by developers
posting test results), we should definitely track this
down before release.

Thanks,
Ranjit.

- --
Ranjit Mathew       Email: rmathew AT gmail DOT com

Bangalore, INDIA.     Web: http://ranjitmathew.hostingzero.com/




-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFDo2ZUYb1hx2wRS48RAmf7AJ9k74ul87x48fJZtc9LOWmIX1DvrgCeIJYD
PvtJ4o641+vFyYIYGLfHgS4=
=ZZV7
-----END PGP SIGNATURE-----