Matt, It looks like the problem here lies within boost itself.
Until boost 1.47 a deadlock condition existed durring concurrent condition_wait() and interrupt() calls, which is what we are running into. this seems to happen most commonly as a TPB thread body is blocking on an input condition variable while the python/top-level thread is calling unlock() --> interrupt() which blocks on a thread_info mutex. see https://svn.boost.org/trac/boost/ticket/4978 The boost minimum requirement in GNU Radio should probable be raised to 1.47 (or at least some kind of warning added) in order to avoid this behavior in the future. test2.py seems to run without any issues or deadlock using boost 1.48 from source. -Tim On 12/16/2011 04:45 PM, Matt Mills wrote: > All, > > I'm willing to offer a 100$ bounty on a patch that fixes the GNUradio > lockup in the attached script (basically just running lock() unlock() > in a loop). > > Thanks, > Matt. > > ---------- Forwarded message ---------- > From: *Matt Mills* <mmi...@2bn.net <mailto:mmi...@2bn.net>> > Date: Fri, Dec 9, 2011 at 9:02 AM > Subject: Re: [Discuss-gnuradio] Gnuradio locking up > To: Don Ward <don2387w...@sprynet.com <mailto:don2387w...@sprynet.com>> > > > Don, > > File is attached; If you watch CPU use, on my system it goes to about > 40% for 5-10 seconds and then drops to 0%. Once it has dropped to 0 it > has locked up. > > -MM > > > On Fri, Dec 9, 2011 at 8:32 AM, Don Ward <don2387w...@sprynet.com > <mailto:don2387w...@sprynet.com>> wrote: > > Matt, > > Could you email me a copy of your simplest test example that > fails? I would like to look at it. How long does it run before > it fails? > > Thanks, > > -- Don W. > > > > > _______________________________________________ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
_______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
