Re: [Discuss-gnuradio] benchmark_rx.py segmentation fault

2015-05-01 Thread Martin Braun
Did you update GNU Radio *after* you updated UHD? If not, that's what you should do. http://gnuradio.org/redmine/projects/gnuradio/wiki/FAQ#My-application-segfaults-immediately-It-used-to-work-and-I-didnt-change-it-What-the M On 30.04.2015 08:59, Richard Bell wrote: Hello, I'm using Ubuntu

Re: [Discuss-gnuradio] benchmark_rx.py segmentation fault

2015-05-01 Thread Richard Bell
I use pybombs to update, which automatically updates UHD first and then GNU Radio. Rich On Fri, May 1, 2015 at 10:20 AM, Martin Braun martin.br...@ettus.com wrote: Did you update GNU Radio *after* you updated UHD? If not, that's what you should do.

Re: [Discuss-gnuradio] benchmark_rx.py segmentation fault

2015-05-01 Thread Henry Jin
I remember I had the same issue before when testing the benchmark. What I did to avoid the crash is to start the tx first, and then the rx. It seems that you are doing it in reverse order, which is reasonable but not working according to my test. On Fri, May 1, 2015 at 10:51 AM, Richard Bell

Re: [Discuss-gnuradio] benchmark_rx.py segmentation fault

2015-05-01 Thread Martin Braun
OK, then I have no clue. If you can present a stack trace here, someone might have a better idea. Cheers, Martin On 01.05.2015 10:51, Richard Bell wrote: I forgot to mention that I also re-cloned pybombs before doing the update. So to be explicit, I deleted the target and pybombs directory. I

Re: [Discuss-gnuradio] benchmark_rx.py segmentation fault

2015-05-01 Thread Richard Bell
I forgot to mention that I also re-cloned pybombs before doing the update. So to be explicit, I deleted the target and pybombs directory. I then re-cloned pybombs and performed a new ./pybombs install gnuradio. This recognized I had all dependencies installed via rpm and only needed to remove and

[Discuss-gnuradio] benchmark_rx.py segmentation fault

2015-04-30 Thread Richard Bell
Hello, I'm using Ubuntu 14.04, gnuradio 3.7.8, USRP N210 and the latest UHD. Everything was recently (3 days ago) updated to newest versions and USRP's reflashed. I have custom flowgraphs that use the USRP N210's that work fine. I decided to play around with the benchmark_tx and benchmark_rx