Re: [Discuss-gnuradio] Volk machine: ssse3_32 segmentation faults (was RE: How to diagnose make test failures)

[Tom Rondeau]

On Tue, Apr 23, 2013 at 10:37 AM, Stamper, Brian <address@hidden> wrote:
> Hi all,
>
> Previously I posted that I was getting the following make test failures. I'm 
> building GNU Radio in Fuduntu (a fork of Fedora) on a 32-bit Intel Atom N270 
> based netbook (an Asus Eee 1000).
>
>>
>> 22/192 Test #22: qa_fft_filter ....................***Failed 1.05 sec
>> 85/192 Test #85: test_gr_filter ...................***Failed 0.27 sec
>> 91/192 Test #91: qa_fft_filter ....................***Failed 1.11 sec
>> 92/192 Test #92: qa_hilbert .......................***Failed 1.09 sec
>> 93/192 Test #93: qa_filter_delay_fc ...............***Failed 1.10 sec
>> 94/192 Test #94: qa_pfb_arb_resampler .............***Failed 1.13 sec
>> 95/192 Test #95: qa_rational_resampler ............***Failed 1.23 sec
>> 97/192 Test #97: qa_fir_filter ....................***Failed 1.23 sec
>
> I started running the test shell scripts individually and found that they all 
> crashed with the same message:
>
> Using Volk machine: ssse3_32
> Segmentation fault
>
> I believe all of my code and dependencies are up to date, but maybe there is 
> some unlisted dependency I'm missing?
>
>
> Thanks,
>
> Brian Stamper

Hi Brian,

No, this isn't a dependency issue. Might be an issue with the
machine/processor you have. But still, the segmentation fault isn't
necessarily related to Volk. That's just a message that's always
printed when using Volk.

The best way to get info from here is to use gdb. In one of the QA
test files (the Python file that's in the source tree), add the lines:

import os
print os.getpid()
raw_input()

Do this before any other Python code. When you run it now, it will
print the PID of the process. In another terminal, run gdb (probably
as root), and then run 'attach <pid>' where <pid> is the PID printed
by the program. Then press 'c' to continue in gdb. On the other
terminal running the QA code, press enter (to proceed past the
'raw_input' line). Wait until it crashes, then, in gdb, type 'bt' to
get a back trace. Send that along and it will help us figure out where
the seg fault is happening.

Tom