[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Discuss-gnuradio] Segmentation fault when running usrp_spectrum_sen
From: |
Eric Blossom |
Subject: |
Re: [Discuss-gnuradio] Segmentation fault when running usrp_spectrum_sense.py |
Date: |
Wed, 7 Nov 2007 11:59:00 -0800 |
User-agent: |
Mutt/1.5.9i |
On Tue, Nov 06, 2007 at 03:00:19PM -0800, Eric Blossom wrote:
> On Tue, Nov 06, 2007 at 01:35:17PM -0800, Ruby Lin wrote:
> >
> > Hi all,
> >
> > I updated my gnuradio to gnuradio-3.1.0. And when I run
> > usrp_spectrum_sense.py, it gives the output like:
> >
> > ==============================
> > $ sudo ./usrp_spectrum_sense.py 400M 450M
> > Using RX d'board A: TV Rx Rev 2
> > gain = 57.5
> > Segmentation fault
> > ==============================
> >
> > Could anyone give any suggestion on how to solve it? I can receive the FM
> > radio stations, and other script works fine. I don't know why this
> > happened?
> >
> > Thanks,
> > Roseline
It seems that this is a Python 2.4 vs 2.5 issue, not 32-bit vs 64-bit.
2.5 works, 2.4 segfaults.
Given that the trunk and 3.1 branch are now creating threads
independent of python, it may be that there is some "one time,
per-thread" init that may be required under 2.4.
We are using
PyGILState_Ensure() and PyGILState_Release(d_gstate)
in gr_feval.i. It may be that there's a known python 2.4 bug that we
need to work around.
Could somebody please check this out?
I suggest starting with the python bug tracker.
Thanks,
Eric