Re: Seg fault with test_sparse.m

[Joe Koski]

Quentin,

The patch solved the legend.m problem, with a minor side effect, I now get
messages from gnuplot:

gnuplot> pl '/var/tmp/oct-mUlax1' t "" w lines 3
                                                  ^
         line 0: all points y value undefined!

but the resulting plot is OK in both AquaTerm and print .eps formats.

Everything I need now works with octave-2.9.7, so I don't need to switch
back to 2.1.73. Thanks.

Joe


on 8/3/06 3:10 PM, Quentin Spencer at address@hidden wrote:

> Joe Koski wrote:
>> Hi all,
>> 
>> After getting a successful build of octave-2.9.7 on my Mac G5 with OS X
>> 10.4.7, Xcode tools 2.3 (gcc-4.0.1) and gfortran, I installed dejaGNU and
>> ran make check. I got one IO error, but things were going well until I hit
>> test_sparse. There I got a seg fault. I have attached the terminal output
>> and fntest.log output in case you want to see them.
>> 
>> I then moved to the test directory and ran octave. Here's what I got:
>> 
>> octave:1> test_sparse
>> writing test output to sptest.log
>>   
>>>>>>> /Tools/octave-2.9.7/test/test_sparse.m
>>>>>>>            
>> warning: Calculating Sparse Matrix Type
>> panic: Bus error -- stopping myself...
>> Bus error
>> Joe-Koskis-Computer:/Tools/octave-2.9.7/test jakoski$
>> 
>> I have also attached the sptest.log for your information.
>> 
>> To my untrained eye, the script seems to be running through quite a few
>> tests before the failure. Things are almost working.
>> 
>> Anyway, I'll be available to try things, but maybe it's time for someone
>> with sparse matrix knowledge (definitely not me) to try this on a Mac. I'll
>> be available to assist anyone who wants to try building octave-2.9.7 or
>> later on a Mac under OS X 10.4. I can cut many hours from the build process
>> with my experience from the last few days.
>>   
> 
> I just tried the sparse tests (Fedora 5 system) and I am seeing 3
> failures out of 1176. I'm not getting segfaults, but I haven't looked
> any further to see what the errors are.
> 
>> The other problem that I have is with the legend.m routine in octave-forge.
>> The problem is persistent with any script that uses legend. As I said, I can
>> file a bug report, if it is an unknown problem.
>>   
> 
> The last release of octave-forge does have a bug in legend. I've checked
> the fix into CVS, but I'm attaching the patch.
> 
> Quentin
> 
> Index: main/plot/legend.m
> ===================================================================
> RCS file: /cvsroot/octave/octave-forge/main/plot/legend.m,v
> retrieving revision 1.16
> diff -u -r1.16 legend.m
> --- main/plot/legend.m 14 Apr 2006 12:51:14 -0000 1.16
> +++ main/plot/legend.m 11 Jul 2006 16:09:07 -0000
> @@ -195,7 +195,8 @@
>    shell_cmd=["grep \"^", gnuplot_command_plot, " \" '", tmpfilename, "' | ",
> \
>               "sed -e 's/,/ , /g' -e 's/\"/ \" /g'", " | ", \
>               "awk '", awk_prog, "'"];
> -  [status, plot_cmd] = split(system(shell_cmd),"\n");
> +  [status, output] = system(shell_cmd);
> +  plot_cmd = split(output,"\n");
>  
>    # Remove state file and sync file
>