Hi Eugene, ouch, that's a heavy bug, considering we have blocks called agc2 in-tree.
Thanks for reporting this! Do you want to create an issue on https://github.com/gnuradio/gnuradio/issues , or would you prefer we do that? (I'd of course personally prefer you'd, as the discoverer & solver, at least get the authorship of that ticket) Best regards, Marcus On 09.06.2017 00:02, Eugene Grayver wrote: > We figured out the cause of this error. I had a block called 'vector_sink2' > . I also have blocks called vector_sink. Turns out the block naming simply > appends the block's index to it. > The first vector_sink2 gets called vector_sink21 > The first vector_sink gets called vector_sink1 > So at some point we got an additional 20 vector_sink blocks. So that created > a 'vector_sink21', which had a name conflict with the first vector_sink2. > The moral of the story is not to end the block name with a number. An even > better idea is to add a separator after the block name and its index for the > complete name: e.g. vector_sink2(1) > > > _______________________________________________ > Discuss-gnuradio mailing list > Discuss-gnuradio@gnu.org > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio _______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
