[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 17:33:37 -0400 (EDT) |
Hello,
I am still getting a segmentation fault with that configuration. 'make
check' passed fine. Could it be another call to another library, maybe GUI
related?
I thought someone previously said that the library runs ok in FC3 without
GUI.
Rafael
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
>
- Re: [Discuss-gnuradio] Segmentation fault, (continued)
Re: [Discuss-gnuradio] Segmentation fault, Sachi, 2005/04/02
Re: [Discuss-gnuradio] Segmentation fault, Sachi, 2005/04/02
Re: [Discuss-gnuradio] Segmentation fault, Sachi, 2005/04/03
Re: [Discuss-gnuradio] Segmentation fault, Sachi, 2005/04/04