On Wed, Mar 18, 2009 at 8:01 AM, Eric Blossom
<address@hidden> wrote:
FWIW, your code works for me using the trunk as of r10628.
That is, it prints "Reconfiguring h_block", and then hangs.
(The hang is a different bug that will be addressed soon.)
Is the hang coming from the lock? Since it seems to be crashing once it gets into an infinite loop while locking.
If it printed anything before dying, can you please post that?
Can you generate a backtrace from the segfault using gdb?
(Ignore the file name - I added the "Locking" to see where in the sequence it was crashing)
address@hidden:~/test$ python multiple_top_block_test.py
Reconfiguring h_block
Locking
Segmentation fault
address@hidden:~/test$
And backtrace from gdb: (3.1.3 but same thing happens at the same point in my 3.2 installation)
>>> app.h_block.reconfigure()
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb7d748c0 (LWP 30961)]
gr_hier_block2::lock (this=0xa012a40) at gr_hier_block2.cc:98
98 gr_hier_block2::lock()
Current language: auto; currently c++
(gdb) backtrace
#0 gr_hier_block2::lock (this=0xa012a40) at gr_hier_block2.cc:98
#1 0xb7afa023 in gr_hier_block2_detail::lock (this=<value optimized out>) at gr_hier_block2_detail.cc:369
#2 0xb7af93f0 in gr_hier_block2::lock (this=0xa012a40) at gr_hier_block2.cc:100
#3 0xb7afa023 in gr_hier_block2_detail::lock (this=<value optimized out>) at gr_hier_block2_detail.cc:369
#4 0xb7af93f0 in gr_hier_block2::lock (this=0xa012a40) at gr_hier_block2.cc:100
#5 0xb7afa023 in gr_hier_block2_detail::lock (this=<value optimized out>) at gr_hier_block2_detail.cc:369
#6 0xb7af93f0 in gr_hier_block2::lock (this=0xa012a40) at gr_hier_block2.cc:100
#7 0xb7afa023 in gr_hier_block2_detail::lock (this=<value optimized out>) at gr_hier_block2_detail.cc:369
#8 0xb7af93f0 in gr_hier_block2::lock (this=0xa012a40) at gr_hier_block2.cc:100
This goes on for a looong time (I stopped after 30,000 lines).
Thank you,
Kieran