This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
bad_cast
- To: egcs <egcs dot egcs at cygnus dot com>
- Subject: bad_cast
- From: Nyny <Nyny dot sxthree at penfeld dot tls dot mms dot fr>
- Date: Tue, 28 Jul 1998 10:41:55 +0200
Hi.
I can not find the bad_cast exception in any header.
I'm using snapshot 19980707.
According to the dec96 draft of the standard, still cannot
get a newer one ~:-(
in clause 5.2.7
9 The value of a failed cast to pointer type is the null pointer value
of the required result type. A failed cast to reference type throws
bad_cast (18.5.2).
Is this class defined somewhere I would not expect to find it,
Is it a not yet implemented feature (and then can I expect it
to be implemented soon) or did the standard change ???
##################################################
Something which has nothing to do with the previous.
I've noticed that when using genattrtab (during the build process)
the function rtx_alloc randomly fails returning 0x0000005f instead
of a valid pointer.
This failure was found while compiling native under RH 5.1 on a
Cyrix 6x166p+ box. This did neither occur an a PII 200MHz with
the same OS nor on Solaris 2.5.1.
The problem was rather dificult to track as it did not occur when
running
under a debugger or when printf's slow the things down (which allowed
me to build the complete compiler, and it seems to work al right).
I've never noticed that malloc could fail randomly before this try. Is
there
a bug in the 2.0.34 linux kernel or should I throw my Cyrix away ?
Nyny