Re: [Discuss-gnuradio] usrp_spectrum_sense.py segmentation fault problem

2011-12-21 Thread Sebastian Döring
On Tue, 20 Dec 2011 20:24:28 -0500 Tom Rondeau trondeau1...@gmail.com wrote: On Tue, Dec 20, 2011 at 11:02 AM, Thomas Tsou tt...@vt.edu wrote: On Tue, Dec 20, 2011 at 5:11 AM, Sebastian Döring sdoer...@rhrk.uni-kl.de wrote:

[Discuss-gnuradio] usrp_spectrum_sense.py segmentation fault problem

2011-12-20 Thread Sebastian Döring
Hello list, since I got no answer to my last post, I guess what I wrote wasn´t that helpful. I apologize for whatever I did not understand, but I am not familiar with error logs in the context of the problem I have here. I would really appreciate any help with this. Once again my problem: I

Re: [Discuss-gnuradio] usrp_spectrum_sense.py segmentation fault problem

2011-12-20 Thread Matthias Wilhelm
Hello, judging from the log, it seems that a value conversion to float is going wrong, but my (uneducated) guess the root cause is a race between threads (this script starts quite a number of threads ..?). I would try to enter larger values for the delays (tune, dwelling delay) and see

Re: [Discuss-gnuradio] usrp_spectrum_sense.py segmentation fault problem

2011-12-20 Thread Sebastian Döring
On Tue, 20 Dec 2011 11:39:39 +0100 Matthias Wilhelm wilh...@informatik.uni-kl.de wrote: Hello, judging from the log, it seems that a value conversion to float is going wrong, but my (uneducated) guess the root cause is a race between threads (this script starts quite a number of threads

Re: [Discuss-gnuradio] usrp_spectrum_sense.py segmentation fault problem

2011-12-20 Thread Thomas Tsou
On Tue, Dec 20, 2011 at 5:11 AM, Sebastian Döring sdoer...@rhrk.uni-kl.de wrote: -- #0  0x0013a455 in sem_post@@GLIBC_2.1 () from /lib/tls/i686/cmov/libpthread.so.0 #1  0x0810ab61 in

Re: [Discuss-gnuradio] usrp_spectrum_sense.py segmentation fault problem

2011-12-20 Thread Tom Rondeau
On Tue, Dec 20, 2011 at 11:02 AM, Thomas Tsou tt...@vt.edu wrote: On Tue, Dec 20, 2011 at 5:11 AM, Sebastian Döring sdoer...@rhrk.uni-kl.de wrote: -- #0 0x0013a455 in sem_post@@GLIBC_2.1 ()