How to either diagnose or workaround code that makes octave get stuck

[andrewcd]

Hi All,

I've got a long (~6 hour) monte carlo simulation that I run overnight. 
Recent versions of it have started freezing, maybe one iteration in 100. 
This is annoying because I leave the program chugging away, and then come
back the next morning finding it stuck only a few repetitions in.  No error
message, the OS is quck and crisp, the editor and the rest of the QT
frontend are quick and fine, just no movement in the terminal, and the
command prompt tied up.  

So, two questions:
1.  Is there something that I can do to get octave to skip past a set of
code whenever it has taken to long to run?  
2.  Is it possible to break a process, and then go back and find out what in
the (output suppressed) script got octave stuck?

I'm using 3.2.3 in QtOctave, on a 64 bit Ubuntu 10.04 machine.

Thanks in advance for any help.

--
View this message in context: 
http://octave.1599824.n4.nabble.com/How-to-either-diagnose-or-workaround-code-that-makes-octave-get-stuck-tp4631122.html
Sent from the Octave - General mailing list archive at Nabble.com.