public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Markus Hillebrand <himself@markus-hillebrand.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/8847: dynamic_cast segfaults with shared lib Date: Sat, 18 Jan 2003 00:36:00 -0000 [thread overview] Message-ID: <20030118003600.23788.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/8847; it has been noted by GNATS. From: Markus Hillebrand <himself@markus-hillebrand.de> 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: Sat, 18 Jan 2003 01:30:44 +0100 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit- trail&database=gcc&pr=8847 Hi! Maybe I can provide a hint on that problem ... Today I had some similiar problems by updating some of my libraries and some other sources. I also had a segmentation-fault on a dynamic_cast. After reading this posting I remembered, that problems can occur, when using shared libraries are used without using the -fPIC compiler option. I recompiled the library (omniORB-4.0.0, RedHat 7.3 x-86 Linux, with gcc-3.2.1) and my source with this option and the problem disappeared. I think this is some nasty thing, that there is no (linker) check about that. Maybe someone will provide some more comfortable checkings here ... With best regards, M. Hillebrand
next reply other threads:[~2003-01-18 0:36 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-18 0:36 Markus Hillebrand [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-01-27 15:54 bangerth 2003-01-27 13:06 christoph.wiedemann 2002-12-09 13:46 Reinier.Bezuidenhout 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=20030118003600.23788.qmail@sources.redhat.com \ --to=himself@markus-hillebrand.de \ --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).