On Fri, Aug 31, 2012 at 5:56 PM, Mark Wiebe wrote:
> On Fri, Aug 31, 2012 at 5:35 PM, Ondřej Čertík
> wrote:
>>
>> Hi Dag,
>>
>> On Fri, Aug 31, 2012 at 4:22 AM, Dag Sverre Seljebotn
>> wrote:
>> > On 08/31/2012 09:03 AM, Ondřej Čertík wrote:
>> >> Hi,
>> >>
>> >> There is segfault reported here
On Fri, Aug 31, 2012 at 5:35 PM, Ondřej Čertík wrote:
> Hi Dag,
>
> On Fri, Aug 31, 2012 at 4:22 AM, Dag Sverre Seljebotn
> wrote:
> > On 08/31/2012 09:03 AM, Ondřej Čertík wrote:
> >> Hi,
> >>
> >> There is segfault reported here:
> >>
> >> http://projects.scipy.org/numpy/ticket/1588
> >>
> >> I
Hi Dag,
On Fri, Aug 31, 2012 at 4:22 AM, Dag Sverre Seljebotn
wrote:
> On 08/31/2012 09:03 AM, Ondřej Čertík wrote:
>> Hi,
>>
>> There is segfault reported here:
>>
>> http://projects.scipy.org/numpy/ticket/1588
>>
>> I've managed to isolate the problem and even provide a simple patch,
>> that fi
On 08/31/2012 09:03 AM, Ondřej Čertík wrote:
> Hi,
>
> There is segfault reported here:
>
> http://projects.scipy.org/numpy/ticket/1588
>
> I've managed to isolate the problem and even provide a simple patch,
> that fixes it here:
>
> https://github.com/numpy/numpy/issues/398
>
> however the patch
Hi,
re: valgrind - to get better results you might try the suggestions from:
http://svn.python.org/projects/python/trunk/Misc/README.valgrind
Richard
On 31 August 2012 09:03, Ondřej Čertík wrote:
> Hi,
>
> There is segfault reported here:
>
> http://projects.scipy.org/numpy/ticket/1588
>
> I'v
Hi,
There is segfault reported here:
http://projects.scipy.org/numpy/ticket/1588
I've managed to isolate the problem and even provide a simple patch,
that fixes it here:
https://github.com/numpy/numpy/issues/398
however the patch simply doesn't decrease the proper reference, so it
might leak.
