discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] Debugging polar code crashes


From: Cinaed Simson
Subject: Re: [Discuss-gnuradio] Debugging polar code crashes
Date: Fri, 14 Jul 2017 19:36:33 -0700
User-agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Thunderbird/52.2.1

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,
> 
> 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 try to have a look into the python code of the block
> configurator and make sure, only the BEC functions are called? This
> should fix your GRC problem.
> 
> The configurator automates quite a few things regarding channel
> construction and has a built-in system for cached channel capacities. I
> assume something does not behave as expected here.
> 
> Cheers
> Johannes
> 
> On 14.07.2017 01:47, Cinaed Simson wrote:
>> 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 the commandline?
>>>
>>> Cheers
>>> Johannes
>>
>> Hey, I had that problem too!
>>
>> In my case, all the tests pass - I have the correct version of GSL
>> installed - namely 1.16
>>
>> But I couldn't even load the polar grc files.
>>
>> When I press open on the grc it hangs - the grc was consuming 100% of
>> the cpu.
>>
>> Eventually I had to kill it.
>>
>> I first noticed it in gnuradio-3.7.10. I'm currently running
>> gnuradio-3.7.12git and I just checked and the problem is still there.
>>
>> And I can't generate the python code using grcc - both polar grc
>> examples generate errors.
>>
>> -- Cinaed
>>
>>
>>>
>>>
>>> On 12.07.2017 18:04, Marcus Müller wrote:
>>>> 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
>>>> applications [1].
>>>> The idea is to simply execute your minimal crashing example using
>>>>
>>>> gdb --args python2 /path/to/flowgraph.py
>>>> (gdb) run
>>>> <wait for crash>
>>>> (gdb) backtrace
>>>>
>>>> and figure out why where how things crash. If you got a backtrace, and
>>>> don't immediately see how to proceed (hint: print a few local
>>>> variables,
>>>> if possible, using gdb's "print" command), share it with the mailing
>>>> list
>>>>
>>>> Best regards,
>>>> Marcus
>>>>
>>>> [1]https://wiki.gnuradio.org/index.php/TutorialsGDB
>>>> On 07/12/2017 05:50 PM, Alex Homero Rivadeneira Erazo wrote:
>>>>> I am using ubuntu 16.04 LTS.
>>>>>
>>>>> At the end of the make test, I have obtained some failures:
>>>>>
>>>>> 97% tests passed, 6 tests failed out of 218
>>>>>
>>>>> Total Test time (real) = 142.49 sec
>>>>>
>>>>> The following tests FAILED:
>>>>> 48 - qa_ctrlport_probes (Failed)
>>>>> 59 - qa_cpp_py_binding (Failed)
>>>>> 76 - qa_cpp_py_binding_set (Failed)
>>>>> 124 - qa_filterbank (Failed)
>>>>> 154 - qa_ofdm_txrx (Failed)
>>>>> 197 - qa_fading_model (Failed)
>>>>> Errors while running CTest
>>>>> Makefile:61: recipe for target 'test' failed
>>>>> make: *** [test] Error 8
>>>>>
>>>>> Best regards,
>>>>>
>>>>> Alex
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Jul 12, 2017 at 11:46 AM, Marcus Müller
>>>>> <address@hidden <mailto:address@hidden>> wrote:
>>>>>
>>>>>     That might still give us enough debug info. Which Linux distro are
>>>>>     we talking about (or, is it Linux at all?)
>>>>>
>>>>>     Best regards,
>>>>>
>>>>>     Marcus
>>>>>
>>>>>
>>>>>     On 07/12/2017 05:30 PM, Alex Homero Rivadeneira Erazo wrote:
>>>>>>     Hi Marcus
>>>>>>
>>>>>>     At this moment, I am installing the
>>>>>>     gnuradio 3.7.12git-171-get72c77bc from source, which is the same
>>>>>>     that I installed with pybombs . Unfortunately, I just already
>>>>>>     built the gnuradio with "make && make test". The gnuradio that I
>>>>>>     had with the standard installation was gnuradio 3.7.9
>>>>>>
>>>>>>     Thanks
>>>>>>
>>>>>>     Best regards,
>>>>>>
>>>>>>     Alex
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>     On Wed, Jul 12, 2017 at 11:13 AM, Marcus Müller
>>>>>>     <address@hidden <mailto:address@hidden>>
>>>>>> wrote:
>>>>>>
>>>>>>         Hi Alex,
>>>>>>
>>>>>>         that does indeed sound like a bug. Things shouldn't be
>>>>>> crashing!
>>>>>>
>>>>>>         So, what's the distribution you're working with? Maybe I can
>>>>>>         help you a bit with the debugging. If you're, at the moment,
>>>>>>         building GNU Radio, make sure that the CMake parameters
>>>>>>         contain -DCMAKE_BUILD_TYPE=RelWithDebInfo , so that we get
>>>>>>         debugging symbols :)
>>>>>>
>>>>>>         Best regards,
>>>>>>
>>>>>>         Marcus
>>>>>>
>>>>>>
>>>>>>         On 07/12/2017 05:11 PM, Alex Homero Rivadeneira Erazo wrote:
>>>>>>>         Hi Marcus
>>>>>>>
>>>>>>>         Based on your suggestion I have deleted my Nabbles account.
>>>>>>>
>>>>>>>         Respect to my problem with the POLAR code
>>>>>>>         configurator block, I checked the discussion threads, but
>>>>>>>         anyone gave a solution.
>>>>>>>
>>>>>>>         Note that this problem does not happen with
>>>>>>>         a gnuradio installed with the distribution's package manager
>>>>>>>         (standard installation). However, the problem with this
>>>>>>>         installation method is that gnuradio is not up to date and
>>>>>>>         it does not have all the blocks that I need in my work. That
>>>>>>>         is why I used pybombs to install gnuradio which has the
>>>>>>>         blocks that I need. Now the problem is that gnuradio with
>>>>>>>         pybombs does work with the POLAR code configurator block.
>>>>>>>         When I drop the POLAR code configurator block on the canvas,
>>>>>>>         the gnuradio program turns down.
>>>>>>>
>>>>>>>         At this moment, I am installing gnuradio from source. If you
>>>>>>>         have other ideas please tell me.
>>>>>>>
>>>>>>>         Thanks
>>>>>>>
>>>>>>>         Best regards,
>>>>>>>
>>>>>>>         Alex
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>         On Wed, Jul 12, 2017 at 9:43 AM, Marcus Müller
>>>>>>>         <address@hidden <mailto:address@hidden>>
>>>>>>>         wrote:
>>>>>>>
>>>>>>>             Hi Alex,
>>>>>>>
>>>>>>>             I hope you do get an answer, but that mail from Jose is
>>>>>>>             from the
>>>>>>>             beginning of 2016 – not extremely likely.
>>>>>>>
>>>>>>>             Anyway, have you seen the other answers that Jose got?
>>>>>>>             If not: That's Nabble's fault. I never tire to repeat:
>>>>>>>             Nabble is just a terrible, terrible web frontend to use
>>>>>>>             the official GNU
>>>>>>>             Radio Mailing list.
>>>>>>>
>>>>>>>             It's not the official mailing list archive. It never
>>>>>>>             was, and it never
>>>>>>>             will be. The official way to sign up for the mailing
>>>>>>> list is
>>>>>>>
>>>>>>>             https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>>>>>>            
>>>>>>> <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio>
>>>>>>>
>>>>>>>             and there's a link to the official mailing list archive,
>>>>>>>             too.
>>>>>>>
>>>>>>>             I'd recommend deleting your Nabble account, and directly
>>>>>>>             signing up
>>>>>>>             under the above address with your email account. It's
>>>>>>>             really easier to
>>>>>>>             use a proper email client (eg. GMail's web frontend) and
>>>>>>>             simply the
>>>>>>>             mails than Nabble. Nabble breaks discussion threads, it
>>>>>>>             makes answers
>>>>>>>             invisible, and it has cost us hours and hours of
>>>>>>>             unnecessary work so
>>>>>>>             far. PLEASE, don't use Nabble.
>>>>>>>
>>>>>>>             Best regards,
>>>>>>>
>>>>>>>             Marcus
>>>>>>>
>>>>>>>
>>>>>>>             On 07/12/2017 01:52 PM, Alex Rivadeneira wrote:
>>>>>>>             > Dear Jose
>>>>>>>             >
>>>>>>>             > Can you tell me if you solved the problem with the
>>>>>>>             POLAR code configurator
>>>>>>>             > block? because I have the same problem in the gnuradio
>>>>>>>             installed with
>>>>>>>             > pybombs.
>>>>>>>             >
>>>>>>>             > Thanks
>>>>>>>             >
>>>>>>>             > Alex
>>>>>>>             >
>>>>>>>             >
>>>>>>>             >
>>>>>>>             > --
>>>>>>>             > View this message in context:
>>>>>>>
>>>>>>> http://gnuradio.4.n7.nabble.com/polar-code-example-tp58407p64520.html
>>>>>>>
>>>>>>>
>>>>>>> <http://gnuradio.4.n7.nabble.com/polar-code-example-tp58407p64520.html>
>>>>>>>
>>>>>>>
>>>>>>>             > Sent from the GnuRadio mailing list archive at
>>>>>>> Nabble.com.
>>>>>>>             >
>>>>>>>             > _______________________________________________
>>>>>>>             > Discuss-gnuradio mailing list
>>>>>>>             > address@hidden
>>>>>>> <mailto:address@hidden>
>>>>>>>             >
>>>>>>>             https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>>>>>>            
>>>>>>> <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio>
>>>>>>>
>>>>>>>
>>>>>>>             _______________________________________________
>>>>>>>             Discuss-gnuradio mailing list
>>>>>>>             address@hidden
>>>>>>> <mailto:address@hidden>
>>>>>>>             https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>>>>>>            
>>>>>>> <https://lists.gnu.org/mailman/listinfo/discuss-gnuradio>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>         --
>>>>>>>         Regards,
>>>>>>>
>>>>>>>         Alex Homero Rivadeneira E.
>>>>>>>         Cell: 438 397-8330 <tel:%28438%29%20397-8330>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>     --
>>>>>>     Regards,
>>>>>>
>>>>>>     Alex Homero Rivadeneira E.
>>>>>>     Cell: 438 397-8330 <tel:%28438%29%20397-8330>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> -- 
>>>>> Regards,
>>>>>
>>>>> Alex Homero Rivadeneira E.
>>>>> Cell: 438 397-8330
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Discuss-gnuradio mailing list
>>>> address@hidden
>>>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>>>
>>>
>>> _______________________________________________
>>> Discuss-gnuradio mailing list
>>> address@hidden
>>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>> .
>>>
>>
>>
>> _______________________________________________
>> Discuss-gnuradio mailing list
>> address@hidden
>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>
> 
> _______________________________________________
> Discuss-gnuradio mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]