Re: [Discuss-gnuradio] Segfault in Polyphase clock sync block

2018-01-21 Thread Jeff Long
Added issue https://github.com/gnuradio/gnuradio/issues/1554 On Sun, Jan 21, 2018 at 7:38 AM, Jeff Long wrote: > Ah, good. I didn't think it needed another +1 but couldn't think of any > other overflow. > > On Sun, Jan 21, 2018 at 7:33 AM, Jeff Long wrote: > >> The forecast function is supposed

Re: [Discuss-gnuradio] Segfault in Polyphase clock sync block

2018-01-21 Thread Jeff Long
Ah, good. I didn't think it needed another +1 but couldn't think of any other overflow. On Sun, Jan 21, 2018 at 7:33 AM, Jeff Long wrote: > The forecast function is supposed to guarantee that there is enough input, > but it might be rounding down in some cases. Could you try adding the "+1" to

Re: [Discuss-gnuradio] Segfault in Polyphase clock sync block

2018-01-21 Thread Jeff Long
The forecast function is supposed to guarantee that there is enough input, but it might be rounding down in some cases. Could you try adding the "+1" to the last line and see if that changes anything? void pfb_clock_sync_ccf_impl::forecast(int noutput_items, gr_v

Re: [Discuss-gnuradio] Segfault in Polyphase clock sync block

2018-01-21 Thread Daniel Estévez
El 21/01/18 a las 12:35, Daniel Estévez escribió: > El 21/01/18 a las 11:39, Daniel Estévez escribió: >> >> out[i+d_out_idx] = d_filters[d_filtnum]->filter(&in[count+d_out_idx]); >> > > Hi all, > > I've been looking at this again and the problem is that in this line, > > count = -134217704 > >

Re: [Discuss-gnuradio] Segfault in Polyphase clock sync block

2018-01-21 Thread Daniel Estévez
El 21/01/18 a las 11:39, Daniel Estévez escribió: > > out[i+d_out_idx] = d_filters[d_filtnum]->filter(&in[count+d_out_idx]); > Hi all, I've been looking at this again and the problem is that in this line, count = -134217704 for some weird reason. Obviously, this causes the SIGSEGV. I'll try

Re: [Discuss-gnuradio] Segfault in Polyphase clock sync block

2018-01-21 Thread Daniel Estévez
El 21/01/18 a las 12:01, Sakthivel Velumani escribió: > Hi Daniel, > > The pfb block sets history() to ensure sufficient amount of input items > are available. Can you provide information on arguments passed to the > pfb block like sps, taps and no. of filters? Hi Sakthivel, The parameters I'm u

Re: [Discuss-gnuradio] Segfault in Polyphase clock sync block

2018-01-21 Thread Sakthivel Velumani
Hi Daniel, The pfb block sets history() to ensure sufficient amount of input items are available. Can you provide information on arguments passed to the pfb block like sps, taps and no. of filters? Best, Sakthivel On Sun, Jan 21, 2018 at 11:39 AM, Daniel Estévez wrote: > Hi all, > > I'm using

[Discuss-gnuradio] Segfault in Polyphase clock sync block

2018-01-21 Thread Daniel Estévez
Hi all, I'm using a Polyphase clock sync block in one of my flowgraphs (https://github.com/daniestevez/gr-satellites/blob/master/apps/picsat.grc) and I'm getting a segmentation fault when running the flowgraph. Using GDB, the problem seems to be in the Polyphase clock implementation, when filteri