[Discuss-gnuradio] foreacast (mis)behavior for gating block

[Jared Dulmage]

I am writing a block that acts as a gate: it only consumes when locked and 
passes samples when unlocked.  The gate state is generally controlled by tags 
on its input stream.  Thus there is no a priori known input/output 
relationship.  When testing, the block performs as expected until some number 
of samples are processed (input to the block) after which it seems general_work 
is no longer called.  Adding a number of debug statements, I find at the point 
of starvation I get the following repeated forecast sequence w/o a call to 
general_work in between

gr::debug :INFO: frame_sync_c0 - Forecast 4096
gr::debug :INFO: frame_sync_c0 - Forecast 2048
gr::debug :INFO: frame_sync_c0 - Forecast 1024
gr::debug :INFO: frame_sync_c0 - Forecast 512
gr::debug :INFO: frame_sync_c0 - Forecast 256
gr::debug :INFO: frame_sync_c0 - Forecast 128
gr::debug :INFO: frame_sync_c0 - Forecast 64
gr::debug :INFO: frame_sync_c0 - Forecast 32
gr::debug :INFO: frame_sync_c0 - Forecast 16
gr::debug :INFO: frame_sync_c0 - Forecast 8
gr::debug :INFO: frame_sync_c0 - Forecast 4
gr::debug :INFO: frame_sync_c0 - Forecast 2
gr::debug :INFO: frame_sync_c0 - Forecast 1

Any suggestions for further investigation would be appreciated.

Jared.
------------------------------------------------------
Jared Dulmage
Engineering Specialist
Digital Comm. and Implementation Dept.
Aerospace Corporation
310-336-3140