public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: <Reinier.Bezuidenhout@nokia.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/8847: dynamic_cast segfaults with shared lib Date: Mon, 09 Dec 2002 13:46:00 -0000 [thread overview] Message-ID: <20021209214606.3481.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/8847; it has been noted by GNATS. From: <Reinier.Bezuidenhout@nokia.com> To: <gcc-gnats@gcc.gnu.org>, <gcc-prs@gcc.gnu.org>, <hans.utz@informatik.uni-ulm.de>, <gcc-bugs@gcc.gnu.org>, <nobody@gcc.gnu.org> Cc: Subject: Re: c++/8847: dynamic_cast segfaults with shared lib Date: Mon, 9 Dec 2002 16:41:28 -0500 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=3Dview%20audit-trail&database=3D= gcc&pr=3D8847 Hi ... I'm running into a similar problem on my system. Mine is a bit more = difficult to trace since it involves a Java JNI call. =20 I have an application that loads a shared library that uses the = dynamic_cast. When using the shared library from a c++ program on the = command line, it works fine. When I do it via a JNI call in segfaults. = I tried the smaller sample program and that too crashed in the same way. Here is some info: [root@comet jni]# gcc -v Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/2.96/specs gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-110) [root@comet jni]# java -version java version "1.4.1_01" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_01-b01) Java HotSpot(TM) Client VM (build 1.4.1_01-b01, mixed mode) Unfortunately here I can't recompile the JVM .... The java was compiled = with : GCC: (GNU) egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)=20 (This is java 1.4.1_01 release) Should I try compiling by lib with gcc 2.91.66 ?? =20 Thanks Reinier
next reply other threads:[~2002-12-09 21:46 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-09 13:46 Reinier.Bezuidenhout [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-01-27 15:54 bangerth 2003-01-27 13:06 christoph.wiedemann 2003-01-18 0:36 Markus Hillebrand 2002-12-06 9:26 Hans Utz 2002-12-06 9:13 bangerth 2002-12-06 8:56 hans.utz
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=20021209214606.3481.qmail@sources.redhat.com \ --to=reinier.bezuidenhout@nokia.com \ --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).