pytave causes segmentation fault in case of octave memory exhaustion error

[Gawron]

Use following code in a python interpreter:

import pytave
pytave.eval(1,"rand(10^10)")

It causes Segmentation fault immediately.

[David Grundberg (individ)]

I'm not surprised that it segfaults. It is not clear what you want me to do about it. Please state what you would rather have Pytave do, or close the bug. Thanks.

[Gawron (gawron)]

In my opinion pytave should raise OctaveError exception.

Please note, that in octave (tested in versions 3.0.1 and 3.2.2) instruction:

rand(10^10)

causes following error:

error: memory exhausted or requested size too large for range of Octave's index type -- trying to return to prompt

[David Grundberg (individ)]

Ok. I'm setting this triaged, will reproduce it later. Thanks.

[highegg (highegg)]

I think raising just MemoryError is equally sound, and it is far easier to implement because the std::bad_alloc -> MemoryError translation is built-in. A patch is uploaded. I'm not entirely sure that everything inside Octave is properly cleaned up when std::bad_alloc escapes out of feval or eval_string, but that's better left to Octave itself.
best regards

[Gawron (gawron)]

Your fix works very well. Than You!

[Ahmad Zeeshan (ahmadzn)]

Hi! I am new in this field and want to get pytave. But the problem is that I can not get it from anywhere. Kindly help me.

[David Grundberg (individ)]

Ahmad Zeeshan. Please don't hijack bug reports. Thank you.