make check hangs at chol.cc

View: New views
3 Messages — Rating Filter:   Alert me  

make check hangs at chol.cc

by kahacjde :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

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

kai@LxLap:~/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


make check hangs at chol.cc

by John W. Eaton-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

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
|
| kai@LxLap:~/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

Re: make check hangs at chol.cc

by kahacjde :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


-------- Original-Nachricht --------
> Datum: Mon, 23 Mar 2009 20:27:46 -0400
> Von: "John W. Eaton" <jwe@...>
> An: Kai Habel <kai.habel@...>
> CC: octave maintainers mailing list <maintainers@...>
> Betreff: make check hangs at chol.cc

> 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
> |
> | kai@LxLap:~/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

O.k. I could isolate the problem a bit. After running the inv command octave hangs.

[New Thread 0xb53ed950 (LWP 1087)]
octave:1> inv([1 1 1;1 1 1.2;1 1.05 1])
^C                                    
Program received signal SIGINT, Interrupt.
[Switching to Thread 0xb53ed950 (LWP 1087)]
0xb68b4bbc in dlamc3_@plt () from /usr/local/lib/octave-3.1.54+/liboctave.so
Current language:  auto; currently asm
(gdb) bt
#0  0xb68b4bbc in dlamc3_@plt () from /usr/local/lib/octave-3.1.54+/liboctave.so
#1  0xb716e5b1 in dlamc1_ () from /usr/local/lib/octave-3.1.54+/liboctave.so
#2  0xb716dd8a in dlamc2_ () from /usr/local/lib/octave-3.1.54+/liboctave.so
#3  0xb716e665 in dlamch_ () from /usr/local/lib/octave-3.1.54+/liboctave.so
#4  0xb6126d30 in dgetf2_ () from /usr/lib/liblapack.so.3
#5  0xb612721c in dgetrf_ () from /usr/lib/liblapack.so.3
#6  0xb6c7008a in Matrix::finverse () from /usr/local/lib/octave-3.1.54+/liboctave.so
#7  0xb6c73730 in Matrix::inverse () from /usr/local/lib/octave-3.1.54+/liboctave.so
#8  0xb32a30cc in Finv () from /usr/local/libexec/octave/3.1.54+/oct/i686-pc-linux-gnu/inv.oct
#9  0xb78f7914 in octave_builtin::do_multi_index_op () from /usr/local/lib/octave-3.1.54+/liboctinterp.so
#10 0xb78f728f in octave_builtin::subsref () from /usr/local/lib/octave-3.1.54+/liboctinterp.so
#11 0xb78a8a18 in octave_value::subsref () from /usr/local/lib/octave-3.1.54+/liboctinterp.so
#12 0xb7a3ca99 in tree_index_expression::rvalue () from /usr/local/lib/octave-3.1.54+/liboctinterp.so
#13 0xb7a3a2a4 in tree_index_expression::rvalue1 () from /usr/local/lib/octave-3.1.54+/liboctinterp.so
#14 0xb7a2f8a1 in tree_evaluator::visit_statement () from /usr/local/lib/octave-3.1.54+/liboctinterp.so
#15 0xb7a5305b in tree_statement::accept () from /usr/local/lib/octave-3.1.54+/liboctinterp.so
#16 0xb7a2b50b in tree_evaluator::visit_statement_list () from /usr/local/lib/octave-3.1.54+/liboctinterp.so
#17 0xb7a5307b in tree_statement_list::accept () from /usr/local/lib/octave-3.1.54+/liboctinterp.so
#18 0xb77dfb2e in main_loop () from /usr/local/lib/octave-3.1.54+/liboctinterp.so
#19 0xb7772505 in octave_main () from /usr/local/lib/octave-3.1.54+/liboctinterp.so
#20 0x0804877a in main ()

Does this help and is more information needed?

Kai