Paul A. added the comment:
I believe this problem has been gone since around 2.7.5, so can I close this
myself?
--
resolution: - out of date
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14540
Mark Lawrence added the comment:
Is this still a problem given that we're two years on and up to Python 2.7.7?
--
nosy: +BreamoreBoy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue14540
___
Charles-François Natali neolo...@free.fr added the comment:
I think it's bundled with our copy of libffi.
i'm not familiar - at all - with libffi.
But does it really need a bundled malloc() implementation?
I'd be more than happy to use my own installation of libffi instead, but it
seems
Antoine Pitrou pit...@free.fr added the comment:
I think it's bundled with our copy of libffi.
i'm not familiar - at all - with libffi.
But does it really need a bundled malloc() implementation?
Well, the upstream libffi includes dlmalloc.c, so I guess it somehow
needs it (perhaps only on
Paul A. p...@freeshell.org added the comment:
Yes indeed, sorry for not answering that question the first time.
The trace is complete, and is from python... although most of it is really in
the shared lib rather than the executable.
--
___
Python
Charles-François Natali neolo...@free.fr added the comment:
This stack trace is strange.
Is it really the python binary?
Anyway, if it's segfaulting inside dlmalloc, there's probably not much we can
do.
Actually, I wonder why we still ship it...
--
nosy: +neologix, pitrou
Antoine Pitrou pit...@free.fr added the comment:
Anyway, if it's segfaulting inside dlmalloc, there's probably not much we can
do.
Actually, I wonder why we still ship it...
I think it's bundled with our copy of libffi.
I agree the stacktrace is strange. At the very least it looks
Paul A. p...@freeshell.org added the comment:
I'd be more than happy to use my own installation of libffi instead, but it
seems the --with-system-ffi configure flag doesn't work. I've also opened a
different bug for that.
--
___
Python tracker
New submission from Paul A. p...@freeshell.org:
The following stack trace happened towards the end of a Python-2.7.3rc2 build,
but I also get much the same results with 2.7.2; one difference I noticed was I
didn't think I needed to add -DHAVE_USR_INCLUDE_MALLOC_H there.
running build_scripts
