[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] Re: [bug #30514] Array indexing error?

From: Neil Arnold
Subject: [Octave-bug-tracker] Re: [bug #30514] Array indexing error?
Date: Fri, 23 Jul 2010 09:47:09 -0600
User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv: Gecko/20100713 Lightning/1.0b2 Thunderbird/3.1.1


Thank you for your prompt attention to this matter.  I have one question.

Since this looks to me like a code regression, would there be an earlier Octave Windows release without this problem?

I have other windows code invoked from system calls, so moving everything to Linux is a poor option for me. . . and randomly trying old windows installs doesn't sound too good either . . .

Thanks for all of your efforts!


On 7/22/2010 9:39 AM, Jaroslav Hajek wrote:
Update of bug #30514 (project octave):

                 Category:                    None =>  Interpreter
                   Status:                    None =>  Fixed
              Assigned to:                    None =>  highegg
              Open/Closed:                    Open =>  Closed


Follow-up Comment #1:

The crashes after the out-of-memory error are probably Windows-specific,
because I don't see them on Linux neither in 3.3.51+ nor 3.2.4. Most likely
related to some OctaveForge packages.

The out-of-memory itself is a bug in a workaround for LAPACK's bug in
workspace query. The dependence on number of rows is caused by integer
overflows. Indexing has nothing to do with this.

John, apparently it was you who introduced it with 7486:6a6d2abe51ff for some
reason, so I invite you to take a look at my fix:

I think the workaround needs only be triggered when both n>  m and n>=
mnthrs, because that's the only case when the following block from dgelsd in
lapack 3.2 is met:

!     XXX: Ensure the Path 2a case below is triggered.  The workspace
!     calculation should use queries for all routines eventually.
                MAXWRK = MAX( MAXWRK,
      $              4*M+M*M+MAX( M, 2*M-4, NRHS, N-3*M ) )

and this seems to be the only block that was missing throughout 3.0.0 -
3.1.1. I didn't check earlier LAPACKs.


Reply to this item at:


   Message sent via/by Savannah


Neil Arnold
FemtoScan Corporation
4487 S. Bountiful Ridge Dr.
Bountiful, UT 84010
Ph: (801) 860-2524
Fx: (801) 860-2524
Em: address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]