I was seeing a segfault on the exit of usrp_{fft,oscope}.py, but that
has been fixed by Eric in recent code. This is probably a long shot, but
maybe you're using old or unfixed code. See the following message chain
for details:

http://lists.gnu.org/archive/html/discuss-gnuradio/2005-10/msg00227.html
http://lists.gnu.org/archive/html/discuss-gnuradio/2005-10/msg00235.html

- Lee

On Sat, 2006-01-07 at 00:26 -0500, Marcus Leech wrote:
> http://www.propulsionpolymers.com/usrp_ra_receiver.py
> http://www.propulsionpolymers.com/stripchartsink.py
> 
> Together, they make up a crude total-power/spectral receiver chain for 
> amateur radio astronomy using the USRP
>  and an appropriate daughter card.  Still needs a *lot* of work, but 
> it's promising.
> 
> With the current tarballs, on FC3, it provokes a segfault on exit.  
> Don't know why.  Also, when
>   changing integration time for the total-power part of the chain, it 
> takes a LOOOOONG
>   pregnant pause before resuming the chain.  I suspect those two are 
> related.
> 
> 
> _______________________________________________
> 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

Reply via email to