[Discuss-gnuradio] possible bug with hier_block2_detail::msg_disconnect

[Mark Cottrell]

Hello all,

I am working with gnuradio 3.7.2git-28-g639e154d and I have a hierarchical block with a message output that I have been using as part of a larger flowgraph.  Yesterday I found that whenever I call msg_disconnect on the top block with the hier block as the source, I get an error logged about it having no subscribers.  I verified this by printing out the subscribers in calls to message_port_sub and message_port_unsub.

It seems that when you call msg_connect, the call to message_port_sub is not made until the flowgraph has been flattened, so the subscription does not belong to the hier block, it belongs to the block inside the hier block that has the message output.  However, when you call msg_disconnect, it simply attempts to call message_port_unsub on on the hier block, which fails, as the hier block has no subscriptions.

To get around this, I simply commented out the call to message_port_unsub in msg_disconnect, but this isn't ideal and won't fix the problem in all cases.

So my question is, is this a bug? If so, is it known about, and if not can an issue please be raised to track it?

Thanks,

Mark

---

This email, including any attachments, is only
 for the intended recipient. It is subject to copyright, is confidential
 and may be the subject of legal or other privilege, none of which is 
waived or lost by reason of this transmission.

If you are not an intended recipient, you may not use, disseminate, distribute or reproduce such email, any attachments, or any part thereof. If you have received a message in error, please notify the sender immediately and erase all copies of the message and any attachments.

Unfortunately, we cannot warrant that the email has not been altered or corrupted during transmission nor can we guarantee that any email or any attachments are free from computer viruses or other conditions which may damage or interfere with recipient data, hardware or software. The recipient relies upon its own procedures and assumes all risk of use and of opening any attachments.

---