Re: [Discuss-gnuradio] Lock/Unlock segfaulting

2013-10-07 Thread Tom Rondeau
On Mon, Oct 7, 2013 at 12:10 PM, Tom Rondeau wrote: > On Mon, Oct 7, 2013 at 11:55 AM, Achilleas Anastasopoulos > wrote: >> The temporary fix suggested elsewhere with >> substituting lock() with stop() followed by wait() >> and unlock() with start() was tested and works fine!!! >> >> For now this

Re: [Discuss-gnuradio] Lock/Unlock segfaulting

2013-10-07 Thread Tom Rondeau
On Mon, Oct 7, 2013 at 11:55 AM, Achilleas Anastasopoulos wrote: > The temporary fix suggested elsewhere with > substituting lock() with stop() followed by wait() > and unlock() with start() was tested and works fine!!! > > For now this is sufficient for what I want to do, > although the stop/wait

Re: [Discuss-gnuradio] Lock/Unlock segfaulting

2013-10-07 Thread Achilleas Anastasopoulos
The temporary fix suggested elsewhere with substituting lock() with stop() followed by wait() and unlock() with start() was tested and works fine!!! For now this is sufficient for what I want to do, although the stop/wait/start method works only on the entire top_block and not on individual (hier2

Re: [Discuss-gnuradio] Lock/Unlock segfaulting

2013-10-04 Thread Achilleas Anastasopoulos
I have uploaded a bare minimum example that still has this problem: sinusoid--> throtle --> (ON or OFF block) --> null sink http://web.eecs.umich.edu/~anastas/docs/onoff_flat_test1.py And here is all the output of gdb (it segfaults in unlock() ): (gdb) backtrace #0 0x700b80a0 in volk_

Re: [Discuss-gnuradio] Lock/Unlock segfaulting

2013-10-04 Thread Achilleas Anastasopoulos
Marcus, thanks for the quick reply. Here is the backtrace: Sleep... Unlocking... [Thread 0x7fffbe7fc700 (LWP 29591) exited] [Thread 0x7fffbf7fe700 (LWP 29593) exited] [Thread 0x7fffdbfff700 (LWP 29595) exited] [Thread 0x7fffe0aa7700 (LWP 29594) exited] [Thread 0x7fffbeffd700 (LWP 29592) exited]

Re: [Discuss-gnuradio] Lock/Unlock segfaulting

2013-10-04 Thread Marcus Müller
Hi Achilleas, after skimming through your code, I found no obvious mistakes so far. My guess was that under some circumstances, you connect or disconnect a connection twice or something similarly wicked happens, but I can't see why that should happen. Can you supply us with a backtrace, generated

[Discuss-gnuradio] Lock/Unlock segfaulting

2013-10-04 Thread Achilleas Anastasopoulos
I have a pyhton program (see http://web.eecs.umich.edu/~anastas/docs/onoff_flat_test.py) that based on a button chooser (on/off) rearranges itself. I use lock/unlock to do the disconnection/reconnection. However, I always get segfaults after a couple of changes. The graph is pretty simple: A comp