Hi Guys, On a related note: I am hacking, and seem to loose items when the flowgraph is emptying of data. I have block A producing a single output, and block B consuming that single input, and it seems that when block B is finished (say returns WORK_DONE, or sleeping in its work thread) then I can see that it has produced 100000 elements in nitems_written, but on the consumer those elements will not appear in nitems_read, and run out earlier randomly. What could cause behavior? It is no fun debugging the my program and the scheduler with printf...
Miklos On Sun, Aug 6, 2017 at 1:37 PM, Miklos Maroti <mmar...@gmail.com> wrote: > Hi Marcus, > > I do not know if you or someone else has the expertise on tricking the > scheduler to do the right thing. I would like to implement a tagged > stream interleaver that takes two tagged stream inputs and merges them > into a single stream. Sometimes only one stream will contain packets, > so it cannot rely on waiting for input on all of its inputs (like > tagged_stream_mux does). The problem is what to return in forecast: if > we say that we need at least 1 item on port 0, and the packet comes on > port 1, then we are in trouble as we are blocked essentially till a > packet arrives on port 0. Is it possible to do this intelligently? > > Miklos _______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
