Date: Wed, 9 Aug 2023 00:29:22 +0200 From: Christoph Moench-Tegeder <cmt@burggraben.net> To: Dimitry Andric <dim@freebsd.org> Cc: Mark Millard <marklmi@yahoo.com>, toolchain@freebsd.org Subject: Re: c++: dynamic_cast woes Message-ID: <ZNLBwvwFMdo22k-3@elch.exwg.net> In-Reply-To: <6B6A7C9C-8F82-443D-BBC3-B2263FEAFD79@FreeBSD.org> References: <ZNATMN6sbaxcqE6n@elch.exwg.net> <E0109064-9ED3-483F-A7D9-6588EC07BF1F@yahoo.com> <6B6A7C9C-8F82-443D-BBC3-B2263FEAFD79@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
## Dimitry Andric (dim@FreeBSD.org): > Yes, this is a typical problem when type info is replicated across > dynamic library boundaries. The best thing to prevent this is to > ensure that the key functions for a class (typically constructors > and destructors) are only in one translation unit (object file), > and that object file is only in one .so file. As FreeBSD is basically unsupported from upstream, this sounds like I'm in for quite a bit of fun here. Well. Thanks anyways, Christoph -- Spare Space
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZNLBwvwFMdo22k-3>