[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Octave 3.3.54 snapshot available for ftp
From: |
John W. Eaton |
Subject: |
Re: Octave 3.3.54 snapshot available for ftp |
Date: |
Tue, 23 Nov 2010 03:46:42 -0500 |
On 23-Nov-2010, Fredrik Lingvall wrote:
| Thanks. I got a bit further now. It fails in the sparse doc stuff now
| but this can be related to how the sparse libs are build.
|
| I get this error on the MacBook Pro (i7, Westmere):
|
| <snip>
|
| umn.edu/~saad/software/SPARSKIT/paper.ps[]| |
| [373] [374] [375] [376] [377] [378] [379]
| (spmatrix.eps
| )
| [380]
| (gplot.eps
| )
| [381] [382] [383] [384] [385]
| (spmatrix.eps
| )
| [386]
| (spchol.eps
| ./sparse.texi:1075: Could not open file spchol.eps, ignoring it.
| @epsfgetbb ...Could not open file #1, ignoring it}
| @else address@hidden @other
| = 1...
|
| @next #1->@epsfgetbb {#1}
| @epsfsetgraph {#1}
| @imagexxx ...ysize address@hidden @fi @epsfbox {#1.eps}
| @fi @ifimagevmode
| @medskip...
|
| @image ...true @fi @else @imagexxx #1,,,,,@finish
| @fi
| <argument> @hfil @ignorespaces @image {spchol,4in}
| @unskip @hfil
| @next #1->@line address@hidden @leftskip #1
| @kern @rightskip }
| l.1075 @center @image{spchol,4in}
|
| ?
|
| <must press return here to continue>
|
| <snip>
|
| [695] [696] [697] [698] [699] [700] [701] [702] [703] [704] [705]))
| (./op-idx.texi (Operator Index) [706] (./octave.ops)) [707]
| Overfull \vbox (10.87947pt too high) has occurred while \output is active
| [708] )
| Output written on octave.dvi (722 pages, 2651144 bytes).
| Transcript written on octave.log.
| /usr/bin/texi2dvi: etex exited with bad status, quitting.
| make[3]: *** [octave.dvi] Error 1
| make[3]: Leaving directory `/root/software/octave/hg/octave/doc/interpreter'
| make[2]: *** [all-recursive] Error 1
| make[2]: Leaving directory `/root/software/octave/hg/octave/doc'
| make[1]: *** [all-recursive] Error 1
| make[1]: Leaving directory `/root/software/octave/hg/octave'
| make: *** [all] Error 2
|
| and this error on the Xeon (E5504, Nehalem) server:
|
| <snip>
|
| ../../run-octave -f -q -H -p . --eval "plotimages ('plot3', 'eps');"
|
| ../../run-octave -f -q -H -p . --eval "plotimages ('extended', 'eps');"
|
| ../../run-octave -f -q -H -p . --eval "sparseimages ('gplot', 'eps');"
|
| ../../run-octave -f -q -H -p . --eval "sparseimages ('grid', 'eps');"
|
| ../../run-octave -f -q -H -p . --eval "sparseimages ('spmatrix', 'eps');"
|
| ../../run-octave -f -q -H -p . --eval "sparseimages ('spchol', 'eps');"
| panic: Segmentation fault -- stopping myself...
| attempting to save variables to `octave-core'...
| save to `octave-core' complete
| make[3]: *** [spchol.eps] Segmentation fault
| make[3]: Leaving directory `/root/software/octave/hg/octave/doc/interpreter'
| make[2]: *** [all-recursive] Error 1
| make[2]: Leaving directory `/root/software/octave/hg/octave/doc'
| make[1]: *** [all-recursive] Error 1
| make[1]: Leaving directory `/root/software/octave/hg/octave'
| make: *** [all] Error 2
|
|
| This (taken from doc/interpreter/sparseimages.m) works though:
|
| octave:9> n=100; a = 10*speye(n) +
| sparse(1:n,ceil([1:n]/2),1,n,n)+sparse(ceil([1:n]/2),1:n,1,n,n);
| octave:10> [r2,p2,q2]=chol(a);
| octave:11> whos
| Variables in the current scope:
|
| Attr Name Size Bytes Class
| ==== ==== ==== ===== =====
| a 100x100 5592 double
| n 1x1 8 double
| nm 1x1 8 double
| p2 1x1 8 double
| q2 100x100 2408 double
| r1 20x20 2088 double
| r2 100x100 3992 double
|
| Total is 721 elements using 14104 bytes
I don't see this problem. Building with --enable-64 works for me on a
Debian AMD64 system.
Maybe it is related to this reported bug:
https://savannah.gnu.org/bugs/?31734
? I have not investigated the problem. I don't really understand the
sparse matrix code in Octave very well.
If you run
../../run-octave -f -q -H -p . --eval "sparseimages ('spchol', 'eps');"
separate from make, does it crash? What if you try
../../run-octave -g -f -q -H -p . --eval "sparseimages ('spchol', 'eps');"
That should run the same command but with Octave executing under gdb.
Then you could get a backtrace that might give some clues about the
crash.
jwe
- Re: Octave 3.3.54 snapshot available for ftp, (continued)
- Re: Octave 3.3.54 snapshot available for ftp, Fredrik Lingvall, 2010/11/21
- Re: Octave 3.3.54 snapshot available for ftp, John W. Eaton, 2010/11/22
- Re: Octave 3.3.54 snapshot available for ftp, Fredrik Lingvall, 2010/11/22
- Re: Octave 3.3.54 snapshot available for ftp, Fredrik Lingvall, 2010/11/22
- Re: Octave 3.3.54 snapshot available for ftp, John W. Eaton, 2010/11/22
- Re: Octave 3.3.54 snapshot available for ftp, Fredrik Lingvall, 2010/11/23
- Re: Octave 3.3.54 snapshot available for ftp,
John W. Eaton <=
- Re: Octave 3.3.54 snapshot available for ftp, Fredrik Lingvall, 2010/11/23
- Re: Octave 3.3.54 snapshot available for ftp, Fredrik Lingvall, 2010/11/23