Re: [Numpy-discussion] glibc invalid pointer error

2006-10-30 Thread Fernando Perez
On 10/30/06, Travis Oliphant <[EMAIL PROTECTED]> wrote: > David Huard wrote: > > > Ok, > > I'll update numpy and give it another try tonight. > > > > I just fixed some reference-count problems in f2py today. These were of > the variety that there was a missing decref that would cause the > referen

Re: [Numpy-discussion] glibc invalid pointer error

2006-10-30 Thread Travis Oliphant
David Huard wrote: > Ok, > I'll update numpy and give it another try tonight. > I just fixed some reference-count problems in f2py today. These were of the variety that there was a missing decref that would cause the reference count of certain often-used data-types to increase without bound a

Re: [Numpy-discussion] glibc invalid pointer error

2006-10-30 Thread Fernando Perez
On 10/30/06, Travis Oliphant <[EMAIL PROTECTED]> wrote: > Fernando Perez wrote: > > >On 10/30/06, David Huard <[EMAIL PROTECTED]> wrote: > > > > > >>Hi, > >>I have a script that crashes, but only if it runs over 9~10 hours, with the > >>following backtrace from gdb. The script uses PyMC, and repeat

Re: [Numpy-discussion] glibc invalid pointer error

2006-10-30 Thread Travis Oliphant
Fernando Perez wrote: >On 10/30/06, David Huard <[EMAIL PROTECTED]> wrote: > > >>Hi, >>I have a script that crashes, but only if it runs over 9~10 hours, with the >>following backtrace from gdb. The script uses PyMC, and repeatedly calls (> >>100) likelihood functions written in fortran and

Re: [Numpy-discussion] glibc invalid pointer error

2006-10-30 Thread Fernando Perez
On 10/30/06, Travis Oliphant <[EMAIL PROTECTED]> wrote: > Fernando Perez wrote: > >This sounds awfully reminiscent of the bug I recently mentioned: > > > >http://aspn.activestate.com/ASPN/Mail/Message/numpy-discussion/3312099 > > > > > > It actually looks very much like it. I think the problem ma

Re: [Numpy-discussion] glibc invalid pointer error

2006-10-30 Thread Travis Oliphant
Fernando Perez wrote: >On 10/30/06, David Huard <[EMAIL PROTECTED]> wrote: > > >>Hi, >>I have a script that crashes, but only if it runs over 9~10 hours, with the >>following backtrace from gdb. The script uses PyMC, and repeatedly calls (> >>100) likelihood functions written in fortran and

Re: [Numpy-discussion] glibc invalid pointer error

2006-10-30 Thread David Huard
Ok, I'll update numpy and give it another try tonight. Regards, David2006/10/30, Fernando Perez <[EMAIL PROTECTED]>: On 10/30/06, David Huard <[EMAIL PROTECTED] > wrote:> Hi,> I have a script that crashes, but only if it runs over 9~10 hours, with the> following backtrace from gdb. The script uses

Re: [Numpy-discussion] glibc invalid pointer error

2006-10-30 Thread Fernando Perez
On 10/30/06, David Huard <[EMAIL PROTECTED]> wrote: > Hi, > I have a script that crashes, but only if it runs over 9~10 hours, with the > following backtrace from gdb. The script uses PyMC, and repeatedly calls (> > 100) likelihood functions written in fortran and wrapped with f2py. > Numpy: 1.

[Numpy-discussion] glibc invalid pointer error

2006-10-30 Thread David Huard
Hi, I have a script that crashes, but only if it runs over 9~10 hours, with the following backtrace from gdb. The script uses PyMC, and repeatedly calls (> 100) likelihood functions written in fortran and wrapped with f2py. Numpy: 1.0.dev3327Python: 2.4.3Does this backtrace give enough info t