make check hangs at chol.cc

[John W. Eaton]

On 19-Mar-2009, Kai Habel wrote:

| Hello all,
| with the current tip make check hangs at chol.cc. WhenI interrupt it
| with ctrl+C I see the message:
| "chol: unexpected second or third input". The fntest.log does not
| contain any useful information about the reason. Any ideas?
| 
| Kai
| 
| address@hidden:~/hg-octave/octave> make check
| make -f octMakefile check
| make[1]: Entering directory `/home/kai/hg-octave/octave'
| make -C test check
| make[2]: Entering directory `/home/kai/hg-octave/octave/test'
| ../run-octave --norc --silent --no-history ./fntests.m .
| 
| Integrated test scripts:
| 
|   src/DLD-FUNCTIONS/besselj.cc ........................... PASS  180/180
|   src/DLD-FUNCTIONS/betainc.cc ........................... PASS    6/6
|   src/DLD-FUNCTIONS/bsxfun.cc ............................ PASS   55/55
|   src/DLD-FUNCTIONS/cellfun.cc ........................... PASS   74/74
|   src/DLD-FUNCTIONS/chol.cc ..............................^Cchol:
| unexpected second or third input
| 
| 
| fntest.log:
| >>>>> processing
| # >>>>>  new test file
| # ?????  no tests in file
| # !!!!!  test had an unexpected result
| #   *****  code for the test
| # Search for the unexpected results in the file
| # then page back to find the file name which caused it.
| # The result may be an unexpected failure (in which
| # case an error will be reported) or an unexpected
| # success (in which case no error will be reported).
| >>>>> processing /home/kai/hg-octave/octave/src/DLD-FUNCTIONS/besselj.cc
| >>>>> processing /home/kai/hg-octave/octave/src/DLD-FUNCTIONS/betainc.cc
| >>>>> processing /home/kai/hg-octave/octave/src/DLD-FUNCTIONS/bsxfun.cc
| >>>>> processing /home/kai/hg-octave/octave/src/DLD-FUNCTIONS/cellfun.cc
| >>>>> processing /home/kai/hg-octave/octave/src/DLD-FUNCTIONS/chol.cc
| 

I don't see this problem.

To debug it on your system, I suggest you try extracting the test code
from chol.cc and running it directly in Octave under gdb.  Then when
it hangs, you can interrupt Octave to see where it is stuck.  If it is
in an infinite loop, you may have to step or continue and stop
multiple times to see where the loop is happening.

jwe