I believe I hit the same bug, using extract on a polymorphic type.
In the old code, I used make_constructor, passing object to it, and using
extract.
In the new code, I don't use make_constructor, just use bp::init. My segfault
is gone. Maybe just luck?
__
On 19.05.2012 00:43, Gabe Rives-Corbett wrote:
> Is there any possible workaround to use inheritance with GCC 4.7?
I know of none, sorry. I'd like to use more c++11 features too, but for
now I am forced to stick with 4.6.3. I am working on a bugreport on that
topic though. However, my time is pret
oes it have to do with using std::shared_ptr for storage? If so is there a
> way around this? Any help is appreciated.
>
> --
> Gabe Rives-Corbett
>
> ------ next part ------
> An HTML attachment was scrubbed...
> URL:
> <http://mail.p
It's especially useful to know because this list can expect the same
problem to be reported as a bug in BPL repeatedly from now on :)
Did you submit the bug to GCC's bugzilla, and if you did do you have
a link?
If you didn't, submitting it and having it rejected is worth doing
just so we can l
On 18.05.2012 19:47, Niall Douglas wrote:
> So it was a bug in GCC after all. Useful to know.
Sorry that I forgot to mention. I was pretty sure it was the GCC after I
tried with two different Boost versions and the very same code was
running fine on gcc 4.6.3 platforms. It is not 100% bulletproof,
So it was a bug in GCC after all. Useful to know.
Niall
On 18 May 2012 at 10:41, Jonas Wielicki wrote:
> On 17/05/12 23:42, Gabe Rives-Corbett wrote:
> > I'm getting a seg fault when trying to call a virtual method on a base
> > class from python.
> I had a similar problem a few days ago. Whic
On 17/05/12 23:42, Gabe Rives-Corbett wrote:
> I'm getting a seg fault when trying to call a virtual method on a base class
> from python.
I had a similar problem a few days ago. Which g++ version are you using?
I had problems with 4.7.0 (redhat) while 4.6.3 (redhat) was working fine.
--
Jonas
_
