[Top][All Lists]

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

Re: [Discuss-gnuradio] Segmentation fault

From: Tom Rondeau
Subject: Re: [Discuss-gnuradio] Segmentation fault
Date: Mon, 20 Feb 2012 17:42:03 -0500

On Mon, Feb 20, 2012 at 5:48 AM, Jorge Hernandez <address@hidden> wrote:
Hi all,

I've been working lately to get to work the mimo files from trondeau's branch. After some trials, I thought I've successfully merged the master branch into this branch so I could use the mimo files. However,  when trying to run the benchmark_mimo_ofdm.py file a segmentation fault is happening. I've been reading about this error but I don't know yet where it comes from. I've checked the "How do I debug GNU Radio in Python" from the FAQ to see what to do in this case. I've followed the 2 steps suggested in this point but I don't understand the results coming from the (gdb) backtrace. If anyone has experience with this problem or knows how to understand this message I would really appreciate any help. I enclose the messages I'm getting.

This is what it shows when trying to run benchmark_ofdm_mimo.py:

linux; GNU C++ version 4.4.1 [gcc-4_4-branch revision 150839]; Boost_103900; UHD_003.004.000-122b947

Press Enter to continue
Noise voltage:  4.472135955
Frequency offset:  0
Symbols per Packet:  16.0
Samples per Packet:  11520.0
>>> gr_fir_ccf: using 3DNow!
>>> gr_fir_ccc: using 3DNow!Ext
>>> gr_fir_fff: using 3DNow!
Transmitter using  1
Receiver using     2

After following the steps suggested it shows:

(gdb) backtrace
#0  gr_ofdm_alamouti_frame_acquisition::calculate_equalizer (this=0x1137c40, channel=<value optimized out>, symbol=<value optimized out>,
    zeros_on_left=<value optimized out>) at gr_ofdm_alamouti_frame_acquisition.cc:210
#1  0x00007f4b40673f67 in gr_ofdm_alamouti_frame_acquisition::general_work (this=0x1137c40, noutput_items=<value optimized out>,
    ninput_items=<value optimized out>, input_items=std::vector of length 3, capacity 3 = {...}, output_items=<value optimized out>)
    at gr_ofdm_alamouti_frame_acquisition.cc:245
#2  0x00007f4b40702c65 in gr_block_executor::run_one_iteration (this=0x7f4b187d7f20) at gr_block_executor.cc:378
#3  0x00007f4b407235c2 in gr_tpb_thread_body::gr_tpb_thread_body (this=<value optimized out>, block=...) at gr_tpb_thread_body.cc:49
#4  0x00007f4b4071c20c in boost::detail::function::void_function_obj_invoker0<gruel::thread_body_wrapper<tpb_container>, void>::invoke(boost::detail::function::function_buffer&) () from /usr/local/lib64/libgnuradio-core-3.4.2git.so.0
#5  0x00007f4b4010cd64 in boost::function0<void>::operator() (this=<value optimized out>) at /usr/include/boost/function/function_template.hpp:989
#6  0x00007f4b3fce1010 in thread_proxy () from /usr/lib64/libboost_thread.so.1.39.0
#7  0x00007f4b415d665d in start_thread () from /lib64/libpthread.so.0
#8  0x00007f4b40ce9ecd in clone () from /lib64/libc.so.6
#9  0x0000000000000000 in ?? ()

Thanks in advance,


Hi Jorge,
So what that backtrace is telling you is on the #0 line that the seg fault is occurring here:

So it's that file, line 210.

All that does is narrow your search down for where it's going wrong, but this one isn't going to tell you what's wrong with it.

So you're doing a 1x2 code. I know when Matt and I left off with this branch, there were some definite issues, and this might just be one of them. Have you tried to do a 2x1 MIMO? I'm pretty sure we had that working. I can't really remember...

I'm afraid I can't help you more right now, yo're going to have to look into that file and try to figure out why it's segfaulting one you. But, thanks for reading over the FAQ and posting the back trace! And you figured out how to merge those two branches, so it sounds like you're heading in the right direction!


reply via email to

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