# Solution for SegFault with Lock / Unlock in 3.7 C++

**URL:** <https://www.ruby-forum.com/t/solution-for-segfault-with-lock-unlock-in-3-7-c/240123>\
**Category:** GNU Radio\
**Created:** [March 28, 2014, 5:47pm UTC](https://www.ruby-forum.com/t/solution-for-segfault-with-lock-unlock-in-3-7-c/240123 "2014-03-28T17:47:57Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Detlef\_R](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/58f4c7/32.png) [@Detlef\_R](https://www.ruby-forum.com/u/Detlef_R)\
**Post date:** [March 28, 2014, 5:47pm UTC](https://www.ruby-forum.com/t/solution-for-segfault-with-lock-unlock-in-3-7-c/240123/1 "2014-03-28T17:47:57Z")

</div>

I was wondering if there has been any progress or work arounds for Bug  
598  
in 3.7?

[http://gnuradio.org/redmine/issues/598](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 trunked radio calls and I need  
to  
be able to dynamically connect / disconnect recording flowgraphs as new  
calls are started. The program works fine under 3.6.

I was wondering if there are any work arounds I should try. I have tried  
using tb-\>stop, tb-\>wait, tb-\>start, but it still crashes. Is there  
some  
other way to dynmically connect & disconnect blocks that doesn’t require  
lock / unlock?

Is there an ETA when this would be fixed? Anything I can help on? I am  
going to have to go back to 3.6 if I can’t figure out a solution.

Thanks!

- Luke

---

<div class="post-metadata">

**Author:** ![hagus](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/9de053/32.png) [@hagus](https://www.ruby-forum.com/u/hagus)\
**Post date:** [March 28, 2014, 5:54pm UTC](https://www.ruby-forum.com/t/solution-for-segfault-with-lock-unlock-in-3-7-c/240123/2 "2014-03-28T17:54:58Z")

</div>

What version of boost are you using?

Tim

---

<div class="post-metadata">

**Author:** ![hagus](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/9de053/32.png) [@hagus](https://www.ruby-forum.com/u/hagus)\
**Post date:** [March 28, 2014, 7:26pm UTC](https://www.ruby-forum.com/t/solution-for-segfault-with-lock-unlock-in-3-7-c/240123/3 "2014-03-28T19:26:07Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![hagus](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/h/9de053/32.png) [@hagus](https://www.ruby-forum.com/u/hagus)\
**Post date:** [March 28, 2014, 6:10pm UTC](https://www.ruby-forum.com/t/solution-for-segfault-with-lock-unlock-in-3-7-c/240123/4 "2014-03-28T18:10:45Z")

</div>

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?