Re: [Discuss-gnuradio] Debugging polar code crashes

On 07/17/2017 03:20 AM, Marcus Müller wrote: > Hi Johannes, > > thanks for this very short and informal bug report on your own software :) > > so, a bit of debugging from my side: > > gdb --args python2 $(which gnuradio-companion) > (gdb) run Cool! That's how you debug the XML code. I was

Re: [Discuss-gnuradio] Debugging polar code crashes

Hi Johannes, thanks for this very short and informal bug report on your own software :) so, a bit of debugging from my side: gdb --args python2 $(which gnuradio-companion) (gdb) run … Trigger hangup by dragging POLAR config onto canvas … [ctrl-C] Thread 1 "python2" received signal SIGINT,

Re: [Discuss-gnuradio] Debugging polar code crashes

Hi List, I created an issue for this on github [0]. I assume the bug manifested itself due to a change in GRC. Cheers Johannes [0] https://github.com/gnuradio/gnuradio/issues/1385 On 15.07.2017 04:36, Cinaed Simson wrote: Hi Johannes - I captured the output of grcc for both polar grc

Re: [Discuss-gnuradio] Debugging polar code crashes

Hi Johannes - I captured the output of grcc for both polar grc files and they can't find polar_config I did a search of the gnuradio tree and my home directory find . -name polar_config\* and I couldn't find it either. -- Cinaed On 07/14/2017 01:04 AM, Johannes Demel wrote: > Hi, > >

Re: [Discuss-gnuradio] Debugging polar code crashes

On 07/14/2017 01:04 AM, Johannes Demel wrote: > Hi, > > this is a tricky one. My assumption is, that the configurator block > tries to compute channel capacities with a complex algorithm. There is > also the BEC channel approximation, which should be called. > This whole bug is caused by some GRC

Re: [Discuss-gnuradio] Debugging polar code crashes

Hi, this is a tricky one. My assumption is, that the configurator block tries to compute channel capacities with a complex algorithm. There is also the BEC channel approximation, which should be called. This whole bug is caused by some GRC changes, as far as I could figure it out. Could you

Re: [Discuss-gnuradio] Debugging polar code crashes

On 07/13/2017 12:03 AM, Johannes Demel wrote: > Hi Alex, > > could you be more specific about > 'When I drop the POLAR code configurator block on the canvas, the > gnuradio program turns down.'? > Does GRC quit with an error? Does it turn dark and is unresponsive? Is > there anything printed on

Re: [Discuss-gnuradio] Debugging polar code crashes

Hi Johannes The GNU radio program turns dark and is unresponsive, and there is not anything printed on the command line. Best regards, Alex On Thu, Jul 13, 2017 at 3:03 AM, Johannes Demel wrote: > Hi Alex, > > could you be more specific about > 'When I drop the

Re: [Discuss-gnuradio] Debugging polar code crashes

Hi Alex, could you be more specific about 'When I drop the POLAR code configurator block on the canvas, the gnuradio program turns down.'? Does GRC quit with an error? Does it turn dark and is unresponsive? Is there anything printed on the commandline? Cheers Johannes On 12.07.2017 18:04,

[Discuss-gnuradio] Debugging polar code crashes (was: Re: polar code example)

Those test failures aren't great, but I think they might be bugs in the tests. So, OK, can't remember what you need to do under Ubuntu to get the full Python debugging capability in GDB, but I wrote a (slightly dated, since the python commands have improved) tutorial on debugging crashing Python