Another Java related Segmentation violation on WinXP

[John W. Eaton]

On 25-Jan-2008, Tribo Laboy wrote:

| Hello Michael!
| 
| It seems that the problem is more serious than just Java. I
| uninstalled the Octave 3.0 with all packages. Then re-installed
| without JHandles and Java. The result is that the bug is still there
| and Octave silently disappears. It is difficult to reproduce it. I
| could observe it after repeatedly using the same name of the variable
| to take the output and then changing to a new name like that:
| 
| d = readtext('data.txt')
| d = readtext('data.txt')
| d = readtext('data.txt')
| d = readtext('data.txt')
| d2 = readtext('data.txt')
| 
| The final line crashed it. Later tried without changing the variable
| name and crashed it on the third attempt. The crashing occurs without
| any message from Octave.

I'm unable to reproduce this problem with Octave 3.0.0 on a Debian
system.

| I noticed while modifying and debugging the 'readtext' function that
| there was some problems with the assignment operator. When program was
| stopped in debug mode only the first time a loop was run the
| assignments were made. On repeated loops assignment obviously did not
| work. But it worked while in debug mode. So the same command in the
| body function didn't work but in debug mode worked... Very, very
| strange indeed and I am not sure if this has anything to do with these
| crashes, but ....

If you notice some problem with Octave's debug features, then I think
you'll need to provide a precise description of what you are doing,
what you see happening, and what you expect to happen before anyone
will be able to help with the problem.

jwe