Re: octave segfaulting

[Christoph Ellenberger]

On Thursday 29 April 2010 23.05:29 John W. Eaton wrote:
> On 29-Apr-2010, Christoph Ellenberger wrote:
> | Hi,
> | I just tried to freshly build  the latest development version of octave.
> | After not finding some headers for fltk (thanks Shai) am I now facing a
> | different problem. As soon as I try to start ./run-octave it segfaults
> | (which already happens in the make process during documentation
> | processing). But I can't find any octave-core and also trying gdb
> | ./run-octave only tells me that this file isnt in a executable format. My
> | build environment is a Gentoo Linux, gcc 4.1.2, autoconf 2.63...
> |
> | So my question is how can I debug this issue, and what information (and
> | where can I find/produce it) is needed that this is going to be a useful
> | bug report ?
>
> If you want to run Octave with gdb in the build tree, use
>
>   ./run-octave -g
>
>
> jwe
thanks
now I am getting

[Thread debugging using libthread_db enabled]
[New Thread 0xb56cf710 (LWP 7317)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb56cf710 (LWP 7317)]
0xb7f9a5ec in sigemptyset () 
from /home/christoph/devel/octave/src/.libs/liboctinterp-3.3.51+.so

(gdb) backtrace
#0  0xb7f845ec in sigemptyset () 
from /home/christoph/devel/octave/src/.libs/liboctinterp-3.3.51+.so
#1  0xb76fc299 in octave_set_signal_handler (sig=2, handler=0xb76fc9f0 
<sigint_handler>, restart_syscalls=true) at sighandlers.cc:198
#2  0xb76fc369 in octave_catch_interrupts () at sighandlers.cc:474
#3  0xb76fc45e in install_signal_handlers () at sighandlers.cc:543
#4  0xb76d0d55 in octave_main (argc=6, argv=0xbffbbb34, embedded=0) at 
octave.cc:620
#5  0x080486d8 in main (argc=Cannot access memory at address 0x0
) at main.c:35

and I am quite lost there ... Is this info of any use ?

regards
christoph