public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: David Jung <jungdl@ornl.gov> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/7400: dynamic_cast segfaults with -shared option Date: Fri, 16 Aug 2002 12:36:00 -0000 [thread overview] Message-ID: <20020816193601.9299.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/7400; it has been noted by GNATS. From: David Jung <jungdl@ornl.gov> To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org Cc: Subject: Re: c++/7400: dynamic_cast segfaults with -shared option Date: Fri, 16 Aug 2002 15:27:28 -0400 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7400 As of gcc3.1, dynamic_cast<>() still cannot be used in any programs that use shared libs. Specifically, the version I tried: g++3 (GCC) 3.1 20020604 (Red Hat Linux 7.3 3.1-5) I believe this discussion may be relevant: http://gcc.gnu.org/ml/gcc/2002-06/msg01699.html
next reply other threads:[~2002-08-16 19:36 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-08-16 12:36 David Jung [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-08-22 6:46 David Jung 2002-08-16 13:36 David Jung 2002-07-24 16:26 t6
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20020816193601.9299.qmail@sources.redhat.com \ --to=jungdl@ornl.gov \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).