Re: [Discuss-gnuradio] Segmentation fault in narrowband benchmark_rx.py

[Manu T S]

Thanks for the help. Here is the output.

============================================
address@hidden:narrowband$ gdb python
GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2.1) 7.4-2012.04
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://bugs.launchpad.net/gdb-linaro/>...
Reading symbols from /usr/bin/python...(no debugging symbols found)...done.
(gdb) run benchmark_rx.py -f 900M -m bpsk --rx-gain=25 -r 1M
Starting program: /usr/bin/python benchmark_rx.py -f 900M -m bpsk --rx-gain=25 -r 1M
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7ffff7ffa000
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
linux; GNU C++ version 4.6.3; Boost_104800; UHD_003.006.002-1-g9fd308b3

Using Volk machine: avx_64_mmx_orc
[New Thread 0x7fffe979f700 (LWP 31208)]
[Thread 0x7fffe979f700 (LWP 31208) exited]
[New Thread 0x7fffe979f700 (LWP 31209)]
[Thread 0x7fffe979f700 (LWP 31209) exited]
[New Thread 0x7fffe979f700 (LWP 31210)]
[Thread 0x7fffe979f700 (LWP 31210) exited]
-- Opening a USRP2/N-Series device...
-- Current recv frame size: 1472 bytes
-- Current send frame size: 1472 bytes
[New Thread 0x7fffe979f700 (LWP 31211)]

UHD Warning:
    The recv buffer could not be resized sufficiently.
    Target sock buff size: 50000000 bytes.
    Actual sock buff size: 1000000 bytes.
    See the transport application notes on buffer resizing.
    Please run: sudo sysctl -w net.core.rmem_max=50000000

UHD Warning:
    The recv buffer could not be resized sufficiently.
    Target sock buff size: 50000000 bytes.
    Actual sock buff size: 1000000 bytes.
    See the transport application notes on buffer resizing.
    Please run: sudo sysctl -w net.core.rmem_max=50000000

UHD Warning:
    The send buffer could not be resized sufficiently.
    Target sock buff size: 1048576 bytes.
    Actual sock buff size: 1000000 bytes.
    See the transport application notes on buffer resizing.
    Please run: sudo sysctl -w net.core.wmem_max=1048576
[New Thread 0x7fffe8d91700 (LWP 31212)]

UHD Warning:
    Unable to set the thread priority. Performance may be negatively affected.
    Please see the general application notes in the manual for instructions.
    EnvironmentError: OSError: error in pthread_setschedparam
[New Thread 0x7fffe3fff700 (LWP 31213)]
Warning: Failed to enable realtime scheduling.
[New Thread 0x7fffe37fe700 (LWP 31214)]
[New Thread 0x7fffe2ffd700 (LWP 31215)]
[New Thread 0x7fffe27fc700 (LWP 31216)]
[New Thread 0x7fffe1ffb700 (LWP 31217)]
[New Thread 0x7fffe17fa700 (LWP 31218)]
[New Thread 0x7fffe0ff9700 (LWP 31219)]
[New Thread 0x7fffc7fff700 (LWP 31220)]
[New Thread 0x7fffc77fe700 (LWP 31221)]
[New Thread 0x7fffc6ffd700 (LWP 31222)]
[New Thread 0x7fffc67fc700 (LWP 31223)]
[New Thread 0x7fffc5ffb700 (LWP 31224)]
[New Thread 0x7fffc57fa700 (LWP 31225)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffe0ff9700 (LWP 31219)]
0x00007ffff46534b7 in volk_32fc_32f_dot_prod_32fc_a_sse ()
   from /usr/local/lib/libvolk.so.0.0.0
(gdb)
============================================

On Thu, Feb 27, 2014 at 12:13 AM, West, Nathan <address@hidden> wrote:

> On Wed, Feb 26, 2014 at 11:26 PM, West, Nathan <address@hidden>
> wrote:
>>
>> On Wednesday, February 26, 2014, Tom Rondeau <address@hidden> wrote:
>>>
>>> On Wed, Feb 26, 2014 at 12:01 PM, Manu T S <address@hidden> wrote:
>>> > Hello Everyone,
>>> >
>>> > Not sure if this is already discussed here.
>>> >
>>> > I am facing segmentation fault when running benchmark_rx in narrowband
>>> > examples. It seems like those example used to work fine before, but now
>>> > they
>>> > are having these issues.
>>>
>>>
>>> > Manu T S
>>>
>>>
>>> This could be an issue related to the constellation_receiver QA issue
>>> a few people have seen lately. I can't replicate it on my end, but
>>> Nathan can and is helping to track it down.
>>>
>>> Tom
>>>
>>>
>>
>> That was my first thought as well. At this point we should probably file
>> this in the bug tracker.
>>
>> Manu,
>>
>> Can you send me a backtrace, your processor type, and compiler
>> information?
>>
>> Nathan
>

On Wed, Feb 26, 2014 at 12:33 PM, Manu T S <address@hidden> wrote:
> Hi,
>
> Thanks for the responses.
>
> Output to "lscpu", "cat /proc/cpuinfor", "gcc -v", "python" can be found in
> the link below:
>
> http://home.iitb.ac.in/~manu.ts/cpu-info
>
> I am still figuring out how to get the backtrace.
>

> --
> Manu T S

$ gdb python # this brings up gdb prompt:
(gdb) run benchmark_rx.py -f 900M -m bpsk --rx-gain=25 -r 1M

then it will run, probably crash. then enter
(gdb) bt

Nathan

--
Manu T S