On 23 Jul 2010 at 13:56, Jim Bosch wrote:
> Given that many people (including myself) have pickled Boost.Python
> objects inside dicts many times before without issue, it might be tricky
> to make a contained example that reproduces it this problem. And I'm
> less motivated now because I can j
On 07/23/2010 12:08 AM, Jim Bosch wrote:
I've just run into the "wontfix" problem detailed here:
https://svn.boost.org/trac/boost/ticket/3210
Essentially, shared information held in one module (such as RTTI stuff
needed for dynamic cast) isn't available to another module, leading to
segfaults.
On 23 Jul 2010 at 9:49, Stefan Seefeld wrote:
> On 07/23/2010 09:35 AM, Niall Douglas wrote:
> > I would even go so far as to say that RTLD_LOCAL
> > needs deprecating in GNU libc.
>
> That would open the door for all sorts of ABI issues (symbol collisions
> resulting in the wrong objects bein
On 07/23/2010 09:35 AM, Niall Douglas wrote:
I would even go so far as to say that RTLD_LOCAL
needs deprecating in GNU libc.
That would open the door for all sorts of ABI issues (symbol collisions
resulting in the wrong objects being looked up, etc.).
I don't think making symbols visible glo
On 23 Jul 2010 at 0:08, Jim Bosch wrote:
> I've just run into the "wontfix" problem detailed here:
>
> https://svn.boost.org/trac/boost/ticket/3210
>
> Essentially, shared information held in one module (such as RTTI stuff
> needed for dynamic cast) isn't available to another module, leading to
I've just run into the "wontfix" problem detailed here:
https://svn.boost.org/trac/boost/ticket/3210
Essentially, shared information held in one module (such as RTTI stuff
needed for dynamic cast) isn't available to another module, leading to
segfaults.
I got the impression from reading the
