[Pkg-octave-devel] Bug#532656: Bug#532656: Bug#532656: Bug#532656: Bug#532656: Bug#532656: Bug#532656: Bug#532656: octave3.2_3.2.0-1(mips/unstable): FTBFS on mips. Segfault in regression test.

[John W. Eaton]

On 11-Jun-2009, Rafael Laboissiere wrote:

| * John W. Eaton <jwe at octave.org> [2009-06-11 15:42]:
| 
| > Did you compile the simpler program with the same options used to
| > build Octave?
| 
| Probably not.
| 
| > Can you run Octave under gdb and find where it hangs, either by
| > running
| > 
| >   log2 (complex (0, inf))
| > 
| > and interrupting it when the hang happens and getting a stack trace,
| > or by stepping through the log2 function (and the functions it calls)
| > to find where it hangs?
| 
| When I run it through "./run-octave -g", the command above does not hang,
| but gives immediately this, even when I set a breakpoint at log2:

How did you set the  breakpoint?  You'll need to set it in Flog2 to
stop in Octave's log2 function (the one that is callable from Octave
scripts).

| octave:1> log2 (complex (0, inf))
| 
| Program received signal SIGBUS, Bus error.
| [Switching to Thread 0x2aad4d80 (LWP 11231)]
| 0x2e17ae24 in std::num_put<char, std::ostreambuf_iterator<char, std::char_traits<char> > >::_M_insert_float<double> () from /usr/lib/libstdc++.so.6
| 
| Here is the stack:
| 
| (gdb) bt
| #0  0x2e17ae24 in std::num_put<char, std::ostreambuf_iterator<char, std::char_traits<char> > >::_M_insert_float<double> () from /usr/lib/libstdc++.so.6
| #1  0x2e17b048 in std::num_put<char, std::ostreambuf_iterator<char, std::char_traits<char> > >::do_put () from /usr/lib/libstdc++.so.6
| #2  0x2e18fd44 in std::ostream::_M_insert<double> () from /usr/lib/libstdc++.so.6
| #3  0x2b04e65c in operator<< (os=@0x4328b0, pff=<value optimized out>)
|     at /usr/include/c++/4.3/ostream:214
| #4  0x2b054160 in pr_any_float (fmt=0x2bac0d40, os=@0x4328b0, d=2.2661800709135971, fw=0)
|     at pr-output.cc:1394
| #5  0x2b055ca4 in pr_complex (os=@0x4328b0, c=<value optimized out>, 
|     r_fw=<value optimized out>, i_fw=0, scale=<value optimized out>) at pr-output.cc:1412
| #6  0x2b057a98 in octave_print_internal (os=@0x4328b0, c=@0x455cc8) at pr-output.cc:1958

Can you move to this frame and examine the value of C?

So there is some problem printing the value?  Maybe log2 is returning
some invalid value.

jwe