public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mueller at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/11223] dynamic_cast<> in shared library fails with SegFault when called from JNI
Date: Mon, 29 Sep 2003 19:45:00 -0000 [thread overview]
Message-ID: <20030929174054.16397.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030617154510.11223.mehmet.ozgul@telenity.com>
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11223
------- Additional Comments From mueller at kde dot org 2003-09-29 17:40 -------
Subject: Re: dynamic_cast<> in shared library fails with SegFault when called from JNI
On Sunday 28 September 2003 23:17, you wrote:
> 21:17 ------- Most likely not our bug and no feedback in 2 months. There
> are reports of being able to use dynamic_cast from shared libraries so
> closing.
It is a gcc bug, as it does not work unless you use LTDL_GLOBAL, which is not
a good idea for plugins.
next prev parent reply other threads:[~2003-09-29 17:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030617154510.11223.mehmet.ozgul@telenity.com>
2003-06-29 22:33 ` mueller at kde dot org
2003-07-20 21:12 ` pinskia at physics dot uc dot edu
2003-07-29 20:25 ` pinskia at physics dot uc dot edu
2003-09-28 21:24 ` pinskia at gcc dot gnu dot org
2003-09-29 19:45 ` mueller at kde dot org [this message]
2003-09-29 20:21 ` pinskia at gcc dot gnu dot org
2004-06-16 18:02 ` pinskia at gcc dot gnu dot org
2003-06-17 15:45 [Bug c++/11223] New: " lemehmet@hotmail.com
2003-06-17 15:53 ` [Bug c++/11223] " lemehmet@hotmail.com
2003-06-17 22:10 ` dberlin@gcc.gnu.org
2003-06-19 14:08 ` pinskia at physics dot uc dot edu
2003-06-19 15:55 ` bangerth at dealii dot org
2003-06-19 15:57 ` pinskia at physics dot uc dot edu
2003-06-24 22:44 ` lemehmet at hotmail dot com
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=20030929174054.16397.qmail@sources.redhat.com \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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: link
Be 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).