On 30 March 2012 21:40, mark florisson wrote:
> On 30 March 2012 21:38, mark florisson wrote:
>> On 30 March 2012 19:53, Chris Barker wrote:
>>> On Fri, Mar 30, 2012 at 10:57 AM, mark florisson
>>> wrote:
Although the segfault was caused by a bug in NumPy, you should
probably also con
On 30 March 2012 21:38, mark florisson wrote:
> On 30 March 2012 19:53, Chris Barker wrote:
>> On Fri, Mar 30, 2012 at 10:57 AM, mark florisson
>> wrote:
>>> Although the segfault was caused by a bug in NumPy, you should
>>> probably also consider using Cython, which can make a lot of this pain
On 30 March 2012 19:53, Chris Barker wrote:
> On Fri, Mar 30, 2012 at 10:57 AM, mark florisson
> wrote:
>> Although the segfault was caused by a bug in NumPy, you should
>> probably also consider using Cython, which can make a lot of this pain
>> and boring stuff go away.
>
> Is there a good demo
On Fri, Mar 30, 2012 at 10:57 AM, mark florisson
wrote:
> Although the segfault was caused by a bug in NumPy, you should
> probably also consider using Cython, which can make a lot of this pain
> and boring stuff go away.
Is there a good demo/sample somewhere of an ndarray subclass in Cython?
So
On 29 March 2012 09:07, Christoph Gohle wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> Am 08.03.2012 um 20:39 schrieb Pauli Virtanen:
>
>> 08.03.2012 17:37, Christoph Gohle kirjoitti:
>>> thanks for testing. I have now tried on different platforms. I get
>>> all kinds of crashes on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 08.03.2012 um 20:39 schrieb Pauli Virtanen:
> 08.03.2012 17:37, Christoph Gohle kirjoitti:
>> thanks for testing. I have now tried on different platforms. I get
>> all kinds of crashes on os x (now with numpy 1.6.1) and windows
>> with numpy 1.6.0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 08.03.2012 um 20:39 schrieb Pauli Virtanen:
> 08.03.2012 17:37, Christoph Gohle kirjoitti:
>> thanks for testing. I have now tried on different platforms. I get
>> all kinds of crashes on os x (now with numpy 1.6.1) and windows
>> with numpy 1.6.0
09.03.2012 08:00, Christoph Gohle kirjoitti:
> I don't want to look as if I want other people do my work,
> so I would like to ask if there is a simple way of tracing
> memory leaks (without recompiling the python interpreter)?
The easiest way probably is to compile Numpy with debug symbols on, s
Sure. Check the memcheck tool of Valgrind:
http://valgrind.org/info/tools.html#memcheck
It is a really amazing tool.
Francesc
On Mar 8, 2012, at 11:00 PM, Christoph Gohle wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi again,
>
> I don't want to look as if I want other peop
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi again,
I don't want to look as if I want other people do my work, so I would like to
ask if there is a simple way of tracing memory leaks (without recompiling the
python interpreter)?
Cheers,
Christoph
Am 09.03.2012 um 01:22 schrieb Christoph Go
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
Am 08.03.2012 um 20:39 schrieb Pauli Virtanen:
> 08.03.2012 17:37, Christoph Gohle kirjoitti:
>> thanks for testing. I have now tried on different platforms. I get
>> all kinds of crashes on os x (now with numpy 1.6.1) and windows
>> with numpy 1.6
08.03.2012 17:37, Christoph Gohle kirjoitti:
> thanks for testing. I have now tried on different platforms. I get
> all kinds of crashes on os x (now with numpy 1.6.1) and windows
> with numpy 1.6.0. On Ubuntu with numpy 1.3.0 I get a hughe memory
> leak...
>
> Any hints would be welcome.
The typ
Dear Val,
thanks for testing. I have now tried on different platforms. I get all kinds of
crashes on os x (now with numpy 1.6.1) and windows with numpy 1.6.0. On Ubuntu
with numpy 1.3.0 I get a hughe memory leak...
Any hints would be welcome.
Thanks,
Christoph
Am 08.03.2012 um 09:08 schrieb Va
Hi Christoph,
I've just tried
a=[spampub.UnitArray(i,{'s':i}) for i in xrange(1000)]
and everything looks fine on my side.
Probably my test environment is too different to give comparable results:
In [3]: call(["uname", "-a"])
Linux ubuntu 2.6.35-22-generic #33-Ubuntu SMP Sun Sep 19 20:32:27 UTC
Dear Val,
I agree that more detail is needed. Sorry for that it was late yesterday.
I am running Python 2.6.1, numpy development branch
(numpy-2.0.0.dev_20101104-py2.6-macosx-10.6-universal.egg). maybe I should
switch to release?
I compile with your setup.py using 'python setup.py build_ext -
FWIW, this crashes on Windows with numpy 1.6.1 but not numpy 1.7-git
debug build.
Christoph Gohlke
On 3/7/2012 5:36 PM, Val Kalatsky wrote:
>
> Tried it on my Ubuntu 10.10 box, no problem:
>
> 1) Saved as spampub.c
> 2) Compiled with (setup.py attached): python setup.py build_ext -i
> 3) Tested
Tried it on my Ubuntu 10.10 box, no problem:
1) Saved as spampub.c
2) Compiled with (setup.py attached): python setup.py build_ext -i
3) Tested from ipython:
In [1]: import spampub
In [2]: ua=spampub.UnitArray([0,1,2,3.0],'liter')
In [3]: ua
Out[3]: UnitArray([ 0., 1., 2., 3.])
In [4]: ua.unit
Seeing the backtrace would be helpful.
Can you do whatever leads to the segfault
from python run from gdb?
Val
On Wed, Mar 7, 2012 at 7:04 PM, Christoph Gohle
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi,
>
> I have been struggeling for quite some time now. Desperate as I am, n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I have been struggeling for quite some time now. Desperate as I am, now I need
help.
I was trying to subclass ndarrays in a c extension (see code below) and do
constantly get segfaults. I have been checking my INCREF and DECREF stuff up
and
19 matches
Mail list logo
