Re: [Discuss-gnuradio] free(): invalid pointer for AM demod block at Gnuradio 3.7.13.5
Nice catch, Volker! Glad you're up and running, Ignatius. And you're right, this should be emitting an error message that's actually useful - the output here really didn't help at all. I've opened a bug on Github in reference to this. It should be relatively straight-forward to tackle, which makes it a great issue for a beginner contributor! https://github.com/gnuradio/gnuradio/issues/2493 Cheers, Ben On Tue, May 14, 2019 at 6:27 PM Ignatius Rivaldi wrote: > Ahh that solves it, I thought that was a bandpass filter and passband > frequency is the lower cutoff frequency, thanks > > On Wed, May 15, 2019 at 2:07 AM Volker Schroer wrote: > > > > You have set passband frequency to 0 ! So your passband reaches from 0 > > to 0. That make no sense. Probably a parameter check should be > > introduced to the demod block Further you should add a throttle block > > after your source. > > > > Same problem can be found in 3.8. > > > > > > Am 14.05.19 um 15:02 schrieb Ignatius Rivaldi: > > > I'm running Arch Linux with Gnu Radio 3.7.13.5 and > > > Python 2.7.16 (default, Mar 11 2019, 18:59:25) > > > [GCC 8.2.1 20181127] on linux2 > > > > > > and if I try to use AM demod block with anything the flowgraph crashes > > > with this: > > > > > Warning: This flow graph may not have flow control: no audio or RF > hardware blocks found. Add a Misc->Throttle block to your flow graph to > avoid CPU congestion. > > > > > > Executing: /usr/bin/python2 -u > /home/feanor/Development/SDR/top_block.py > > > > > > free(): invalid pointer > > > > > Done > > > > > > This is just a AM demod block with null sink and null source attached > > > to it, reproduction flowgraph is attached to this email > > > > > > > > > ___ > > > 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 > > ___ > 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
Re: [Discuss-gnuradio] free(): invalid pointer for AM demod block at Gnuradio 3.7.13.5
Ahh that solves it, I thought that was a bandpass filter and passband frequency is the lower cutoff frequency, thanks On Wed, May 15, 2019 at 2:07 AM Volker Schroer wrote: > > You have set passband frequency to 0 ! So your passband reaches from 0 > to 0. That make no sense. Probably a parameter check should be > introduced to the demod block Further you should add a throttle block > after your source. > > Same problem can be found in 3.8. > > > Am 14.05.19 um 15:02 schrieb Ignatius Rivaldi: > > I'm running Arch Linux with Gnu Radio 3.7.13.5 and > > Python 2.7.16 (default, Mar 11 2019, 18:59:25) > > [GCC 8.2.1 20181127] on linux2 > > > > and if I try to use AM demod block with anything the flowgraph crashes > > with this: > > > Warning: This flow graph may not have flow control: no audio or RF > hardware blocks found. Add a Misc->Throttle block to your flow graph to > avoid CPU congestion. > > > > Executing: /usr/bin/python2 -u /home/feanor/Development/SDR/top_block.py > > > > free(): invalid pointer > > > Done > > > > This is just a AM demod block with null sink and null source attached > > to it, reproduction flowgraph is attached to this email > > > > > > ___ > > 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 ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
Re: [Discuss-gnuradio] free(): invalid pointer for AM demod block at Gnuradio 3.7.13.5
You have set passband frequency to 0 ! So your passband reaches from 0 to 0. That make no sense. Probably a parameter check should be introduced to the demod block Further you should add a throttle block after your source. Same problem can be found in 3.8. Am 14.05.19 um 15:02 schrieb Ignatius Rivaldi: I'm running Arch Linux with Gnu Radio 3.7.13.5 and Python 2.7.16 (default, Mar 11 2019, 18:59:25) [GCC 8.2.1 20181127] on linux2 and if I try to use AM demod block with anything the flowgraph crashes with this: Warning: This flow graph may not have flow control: no audio or RF hardware blocks found. Add a Misc->Throttle block to your flow graph to avoid CPU congestion. Executing: /usr/bin/python2 -u /home/feanor/Development/SDR/top_block.py free(): invalid pointer Done This is just a AM demod block with null sink and null source attached to it, reproduction flowgraph is attached to this email ___ 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
[Discuss-gnuradio] free(): invalid pointer for AM demod block at Gnuradio 3.7.13.5
I'm running Arch Linux with Gnu Radio 3.7.13.5 and Python 2.7.16 (default, Mar 11 2019, 18:59:25) [GCC 8.2.1 20181127] on linux2 and if I try to use AM demod block with anything the flowgraph crashes with this: >>> Warning: This flow graph may not have flow control: no audio or RF hardware >>> blocks found. Add a Misc->Throttle block to your flow graph to avoid CPU >>> congestion. Executing: /usr/bin/python2 -u /home/feanor/Development/SDR/top_block.py free(): invalid pointer >>> Done This is just a AM demod block with null sink and null source attached to it, reproduction flowgraph is attached to this email bug2.grc Description: Binary data ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
