Re: [Discuss-gnuradio] Solution for SegFault with Lock / Unlock in 3.7 C++

2014-03-28 Thread Luke Berndt
I am using Boost 1.53, on Ubuntu 13.10 via apt-get. When I was running it under GnuRadio 3.6, I think I was running Boost 1.49, but it got upgrade because I think it is not compatible with GR 3.7? Would it be worth it to try build from source for Boost 1.48 or 1.55? On Fri, Mar 28, 2014 at

Re: [Discuss-gnuradio] Solution for SegFault with Lock / Unlock in 3.7 C++

2014-03-28 Thread Tim Newman
What version of boost are you using? Tim On Fri, Mar 28, 2014 at 12:45 PM, Luke Berndt luk...@gmail.com wrote: I was wondering if there has been any progress or work arounds for Bug 598 in 3.7? http://gnuradio.org/redmine/issues/598 The issue is the GnuRadio will segfault if there are

[Discuss-gnuradio] Solution for SegFault with Lock / Unlock in 3.7 C++

2014-03-28 Thread Luke Berndt
I was wondering if there has been any progress or work arounds for Bug 598 in 3.7? http://gnuradio.org/redmine/issues/598 The issue is the GnuRadio will segfault if there are too many Lock / Unlocks. I am having it happen after 6 - 10 lock/unlocks. My program is a C++ program that records

Re: [Discuss-gnuradio] Solution for SegFault with Lock / Unlock in 3.7 C++

2014-03-28 Thread Tim Newman
I was thinking the older version of boost had a bug in the boost thread stuff that was causing this, but boost 1.53 should be fine. On Fri, Mar 28, 2014 at 1:09 PM, Luke Berndt luk...@gmail.com wrote: I am using Boost 1.53, on Ubuntu 13.10 via apt-get. When I was running it under GnuRadio