[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] Segmentation fault

From: Raphael Cobo
Subject: Re: [Discuss-gnuradio] Segmentation fault
Date: Sun, 3 Apr 2005 20:07:09 -0400 (EDT)


I've put my  output of strace in this file (~.5 Megs)


As you can see there is alot going on behind the screen. I am using the
ssrp board but that may not be the fault. Somewhere at the end you will
see a system call to poen a file that does not exists (there are a lot
more before but they don't sigsev). The file name is :


which is supposed to be in my home dir but it is not. I am running my
board as root and I couldn't find that file anywhere in my system. Could
this be the problem by any chance?


On Sun, 3 Apr 2005, Eric Blossom wrote:

> On Sat, Apr 02, 2005 at 11:03:48PM -0800, Sachi wrote:
> > Hi, Eric
> > 
> > I have checked it with gdb, it returned:
> > 
> > (gdb) continue
> > Continuing.
> > 
> > Program received signal SIGSEGV, Segmentation fault.
> > [Switching to Thread -1208514880 (LWP 1030)]
> > 0x007eb73f in m2fv_64_0 () from
> > /usr/local/lib/libfftw3f.so.3
> > 
> > Then gdb stopped. I didn't use any breakpoints in the
> > code. BTW: I can run the demos provided by wxPython.
> > 
> > Can you sqeeze any information from this? Or what
> > should I do next?
> > Thanks for your time
> > Sachi
> This is good info.  It's blowing up libfftw3f, the FFTW code.
> Haven't ever seen that failure.
> I'd suggest building fftw from source (www.fftw.org) using the
> --enable-single --enable-sse --enable-shared configure options, and
> then after it's built make sure that its "make check" passes.
> If this fixes the problem, there may be a problem with the libfftw3f
> library distributed with FC3.
> Eric

reply via email to

[Prev in Thread] Current Thread [Next in Thread]