Re: [Discuss-gnuradio] [PyBOMBS] Need your help!

2016-05-22 Thread Marcus Müller
Hi Sylvain, what platform are you on? (basically, libalsa should be installed via package whenever possible, which is the case on debian, ubuntu, fedora and centos, I thought) Also: I kind of like the "don't install, just list" idea. However, Pybombs would never encourage you to build stuff as

Re: [Discuss-gnuradio] [PyBOMBS] Need your help!

2016-05-22 Thread Sylvain Munaut
Hi, > My prime test case is the following pybombs command: > > $ pybombs prefix init ~/path/to/prefix -R gnuradio-default > > (Note you will need the most current PyBOMBS and gr-recipes to run this). I just gave this a shot, but I aborted pretty quickly. It started building alsa from sources

Re: [Discuss-gnuradio] GNURadio segmentation fault

2016-05-22 Thread John Shields
On 22/05/16 11:06, Marcus D. Leech wrote: On 05/22/2016 05:19 AM, Marcus Müller wrote: Hi John, I don't really know about the memory usage you see, but: Did you rebuild GNU Radio (and UHD and basically everything you did not install directly through Ubuntu's apt-get)? Upgrading a distro often

Re: [Discuss-gnuradio] Non-uniform behaviour of swigged objects

2016-05-22 Thread Marcus Müller
ha! uhd.tune_request (and others, like sensor_value) python objects have a __nonzero__ method, which is inherently used for conversion to bool, if present. And guess what: they return False. Wondering where they come from. Cheers, Marcus On 22.05.2016 18:02, Marcus Müller wrote: > Well, the

[Discuss-gnuradio] Non-uniform behaviour of swigged objects (was: [USRP-users] uhd.tune_request always returns 0)

2016-05-22 Thread Marcus Müller
Well, the python semantics, at least as I understand them, dictate that "not objectname" is True if objectname is of NoneType, or if objectname is actually False, or evaluates to something that is False (i.e. 0). A valid object "should be". Checking it against the typical swigged GNU Radio

Re: [Discuss-gnuradio] GNURadio segmentation fault

2016-05-22 Thread Marcus D. Leech
On 05/22/2016 05:19 AM, Marcus Müller wrote: Hi John, I don't really know about the memory usage you see, but: Did you rebuild GNU Radio (and UHD and basically everything you did not install directly through Ubuntu's apt-get)? Upgrading a distro often changes the libc version used, and that

Re: [Discuss-gnuradio] GNURadio segmentation fault

2016-05-22 Thread Marcus Müller
Hi John, I don't really know about the memory usage you see, but: Did you rebuild GNU Radio (and UHD and basically everything you did not install directly through Ubuntu's apt-get)? Upgrading a distro often changes the libc version used, and that might mean that the ABI of the very core

[Discuss-gnuradio] GNURadio segmentation fault

2016-05-22 Thread John Shields
Dear All, I have been running GNURadio fairly constantly for a couple of weeks now using simple_ra although, I don't believe it is a problem with that application as HTOP doesn't indicate memory issues etc. I run GNURadio version 3.7.9.1 on an Intel® Core™ i7-2600

Re: [Discuss-gnuradio] How to extract stable fine frequency offset based on the benchmark program?

2016-05-22 Thread somunsfool
Marcus Müller ettus.com> writes: > > Hi, > > Again, I advise *not* to use that. Use the example I mentioned. No one > is really still using the blocks used in benchmark_rx, it's very hard to > get help for them, and they are really not as good as the blocks used in > the example I mentioned.