Bug#188943: g++-3.2: code using dynamic_cast causes segfaults when -fno-rtti is used
Package: g++-3.2
Version: 1:3.2.3-0pre7
Severity: normal
Now obviously, dynamic_cast requires rtti so using -fno-rtti is silly.
I ran into this on a C++ project where we had been using -fno-rtti because rtti
was not used. A recent commit added dynamic_cast code and started segfaulting.
It was believed that the dynamic_cast was at fault and this caused some finger
pointing. Then the no-rtti was noticed.
The compiler should give a warning (or perhaps even an error) if code requiring
rtti is used while the -fno-rtti option is in effect.
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux one 2.4.19 #1 Tue Nov 5 19:53:51 PST 2002 i686
Locale: LANG=C, LC_CTYPE=C (ignored: LC_ALL set)
Versions of packages g++-3.2 depends on:
ii gcc-3.2 1:3.2.3-0pre7 The GNU C compiler
ii gcc-3.2-base 1:3.2.3-0pre7 The GNU Compiler Collection (base
ii libc6 2.3.1-16 GNU C Library: Shared libraries an
ii libstdc++5-dev 1:3.2.3-0pre7 The GNU Standard C++ Library v3 (d
-- no debconf information
Reply to: