On Feb 14, 2012, at 12:59 AM, Martin Braun wrote:
> for those who haven't yet read Tom's recent blog post, I recommend
> it--in a sentence, the lack of applications is hurting GNU Radio, and I
> couldn't agree more.
How about a whole web application which would not exist without GNU Radio?
http
> And this is still the flow-graph that has lock/unlock() in it? From the
> report of very-high
> rescheduling interrupts, I wonder if there's a subtle bug in the Gnu Radio
> block
> scheduler around lock()/unlock() that causes horrible thrashing.
It's pretty easy to get wedged forever if
On Nov 22, 2011, at 7:56 AM, Marcus D. Leech wrote:
> On 22/11/11 10:48 AM, Rachel Kroll wrote:
>> It's pretty easy to get wedged forever if you call lock and unlock a lot in
>> conjunction with connect and disconnect. Sooner or later, you'll hit a race
>> and
> How do you compile this? I put it in a file and made a couple fo quick
> stabs at it.
My Makefile is just:
grlock: grlock.cc
g++ -g -Wall -I/usr/local/include/gnuradio -o grlock grlock.cc \
-lgnuradio-core -Xlinker -rpath /usr/local/lib64
You probably won't need the -Xlinker -r
On Dec 8, 2011, at 1:05 PM, Matt Mills wrote:
> After updating to Ubuntu 11.10 (which has boost 1.46) I still experience the
> lockup.
For the record, I was testing on this:
morbo:~$ cat /etc/slackware-version; uname -a
Slackware 13.37.0
Linux morbo 2.6.37.6 #3 SMP Sat Apr 9 22:49:32 CDT 2011
