Hi Sachi,
I had a similar problem running Fedora Core 3 as a vmware guest (i.e. segmentation fault in libfftw3f). Rebuilding fftw *without* --enable-sse as a configure option fixed it for me.
I hope that helps.
Cheers, Toby
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
--- Eric Blossom <[EMAIL PROTECTED]> wrote:
On Sat, Apr 02, 2005 at 01:21:53PM -0500, Raphael
Cobo wrote:
for the GUI in aHello,
I think this is a bug in the underlying libraries
specific distribution.experience the same
I think that people that use Fedora will
bug. Am I right? Can somebody confirm that the SSEsegmentation fault only
happens in Fedora or Redhat?FYI, It's highly unlikely that this has anything to
do with SSE.
That's just the last message printed before it seg
faulted.
Again, a quick look with gdb will provide real data...
In the stab-in-the-dark department, do the wxPython demos run OK on your system? Not our demos, the ones that you can download from wxpython.org.
Eric
__________________________________ Do you Yahoo!? Yahoo! Personals - Better first dates. More second dates. http://personals.yahoo.com
_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
_______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org http://lists.gnu.org/mailman/listinfo/discuss-gnuradio
