[Top][All Lists]

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

Re: [Discuss-gnuradio] Segmentation fault

From: Toby Oliver
Subject: Re: [Discuss-gnuradio] Segmentation fault
Date: Sun, 03 Apr 2005 10:54:23 +0100
User-agent: Mozilla Thunderbird 1.0 (Windows/20041206)

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.


Sachi wrote:

Hi, Eric

I have checked it with gdb, it returned:

(gdb) continue

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1208514880 (LWP 1030)]
0x007eb73f in m2fv_64_0 () from

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
--- Eric Blossom <address@hidden> wrote:
On Sat, Apr 02, 2005 at 01:21:53PM -0500, Raphael
Cobo wrote:

I think this is a bug in the underlying libraries
for the GUI in a
specific distribution.
I think that people that use Fedora will
experience the same
bug. Am I right? Can somebody confirm that the SSE
segmentation 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

Again, a quick look with gdb will provide real

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.


__________________________________ Do you Yahoo!? Yahoo! Personals - Better first dates. More second dates. http://personals.yahoo.com

Discuss-gnuradio mailing list

reply via email to

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