|
From: | Charles Yee |
Subject: | RE: help with compiling octave-3.3.51 |
Date: | Tue, 29 Jun 2010 21:52:40 +0000 |
Jordi, I did as you instructing and I got the following stack trace. Program received signal SIGSEGV, Segmentation fault. 0x00002b9a6237add8 in sigemptyset () from /usr/local/octave/3.3.51/lib/octave-3.3.51/liboctinterp-3.3.51.so I appreciate your help. Thank you. -charles > Date: Tue, 29 Jun 2010 16:06:19 -0500 > Subject: Re: help with compiling octave-3.3.51 > From: address@hidden > To: address@hidden > CC: address@hidden > > On 29 June 2010 15:44, Charles Yee <address@hidden> wrote: > > > > There was no stack trace. The only error message was "segmentation fault". > > > > I don't know how to generate a stack trace. How would you get octave to > > generate a stack trace? > > You have to generate it yourself, which is why I asked. I hope you > compiled Octave with debug symbols. I think it's the default, but if > not, you'll have to recompile everything with ./configure > --enable-debug $other_options_you_may_have_used. Once you compile in > debug symbols, run octave inside gdb: > > $gdb octave > > Inside gdb, type "run" to run Octave, and once it crashes do "bt" to > get a stack trace. The New Busy is not the too busy. Combine all your e-mail accounts with Hotmail. Get busy. |
[Prev in Thread] | Current Thread | [Next in Thread] |