discuss-gnuradio
[Top][All Lists]
Advanced

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

[Discuss-gnuradio] Segmentation Fault


From: Sriharsha Puranik
Subject: [Discuss-gnuradio] Segmentation Fault
Date: Tue, 18 Oct 2011 19:35:44 -0400

Hi all,

I am facing "Segmentation Fault" error.

My setup is - Ubuntu 11.04, USRP2 with WBX board, gnuradio.

The scenario is - When I run uhd_fft.py, I get the following - 

(gdb) run /usr/local/bin/uhd_fft.py 
Starting program: /usr/bin/python /usr/local/bin/uhd_fft.py
[Thread debugging using libthread_db enabled]
linux; GNU C++ version 4.5.2; Boost_103700; UHD_003.003.000-25f0bd5

[New Thread 0x7fffe1adf700 (LWP 26034)]
[New Thread 0x7fffe12de700 (LWP 26035)]
usrp_source make
Making
-- Opening a USRP2/N-Series device...
[New Thread 0x7fffe0add700 (LWP 26036)]

UHD Warning:
    The recv buffer could not be resized sufficiently.
    Target sock buff size: 50000000 bytes.
    Actual sock buff size: 131071 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: 131071 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: 131071 bytes.
    See the transport application notes on buffer resizing.
    Please run: sudo sysctl -w net.core.wmem_max=1048576

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffe0add700 (LWP 26036)]
0x00007ffff57d6973 in std::_Rb_tree_increment(std::_Rb_tree_node_base*) ()
   from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(gdb) backtrace
#0  0x00007ffff57d6973 in std::_Rb_tree_increment(std::_Rb_tree_node_base*) ()
   from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#1  0x00007ffff419bc68 in tls_destructor ()
   from /usr/lib/libboost_thread.so.1.42.0
#2  0x00007ffff419e177 in thread_proxy ()
   from /usr/lib/libboost_thread.so.1.42.0
#3  0x00007ffff7bc4d8c in start_thread ()
   from /lib/x86_64-linux-gnu/libpthread.so.0
#4  0x00007ffff6a8a04d in clone () from /lib/x86_64-linux-gnu/libc.so.6
#5  0x0000000000000000 in ?? ()
(gdb) 


The UHD logs file has been attached with the mail.

Also, USRP1 with uhd_fft.py is working fine. USRP2 works fine if there is no UI involved (that is - /usr/local/share/uhd/examples/rx_ascii_art_dft  --freq 900e6 --rate 1e6 --dyn-rng 120 works fine).

Can some one please take a look at this problem?

Thanks,
Sriharsha Puranik.

Attachment: uhd.log
Description: Text Data


reply via email to

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