# Qa\_fft\_filter make test failed - seg fault **URL:** \ **Category:** GNU Radio\ **Created:** [January 22, 2014, 2:26am UTC](https://www.ruby-forum.com/t/qa-fft-filter-make-test-failed-seg-fault/238650 "2014-01-22T02:26:04Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Detlef\_R](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/58f4c7/32.png) [@Detlef\_R](https://www.ruby-forum.com/u/Detlef_R)\ **Post date:** [January 22, 2014, 2:26am UTC](https://www.ruby-forum.com/t/qa-fft-filter-make-test-failed-seg-fault/238650/1 "2014-01-22T02:26:04Z")
How can we diagnose make test failures? All tests passed initially, but I had GRC disabled, so I recompiled everything w/ GRC enabled and this test failed. Also, is there a way to re-compile just parts of gnuradio, instead of recompiling everything? 99% of tests past, only qa\_fft\_filter failed on arm build ubuntu 13.10 from source. ubuntu@ubuntu-armhf:~/gnuradio/build$ ctest -V -R qa\_fft\_filter UpdateCTestConfiguration from :/home/ubuntu/gnuradio/build/DartConfiguration.tcl UpdateCTestConfiguration from :/home/ubuntu/gnuradio/build/DartConfiguration.tcl Test project /home/ubuntu/gnuradio/build Constructing a list of tests Done constructing a list of tests Checking test dependency graph… Checking test dependency graph end test 86 Start 86: qa\_fft\_filter 86: Test command: /bin/sh “/home/ubuntu/gnuradio/build/gr-filter/python/filter/qa\_fft\_filter\_test.sh” 86: Test timeout computed to be: 9.99988e+06 86: Segmentation fault 1/1 Test #86: qa\_fft\_filter …\*\*\*Failed 17.72 sec 0% tests passed, 1 tests failed out of 1 Total Test time (real) = 18.32 sec The following tests FAILED: 86 - qa\_fft\_filter (Failed) Errors while running CTest How should I go about diagnosing these problems? Launch GDB and see whats happening? Strange that this is the only test that failed. ---
**Author:** ![kena](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/e9bcb4/32.png) [@kena](https://www.ruby-forum.com/u/kena)\ **Post date:** [January 22, 2014, 10:08am UTC](https://www.ruby-forum.com/t/qa-fft-filter-make-test-failed-seg-fault/238650/2 "2014-01-22T10:08:12Z")
On 01/22/2014 02:24 AM, Ken A. wrote: > How can we diagnose make test failures? All tests passed initially, but > I had GRC disabled, so I recompiled everything w/ GRC enabled and this > test failed. Ken, have you read: [http://gnuradio.org/redmine/projects/gnuradio/wiki/TutorialsDebugging](http://gnuradio.org/redmine/projects/gnuradio/wiki/TutorialsDebugging)? Run ‘ctest -V -R fft\_filter’ to activate verbosity and limit the tests by a regex. > Also, is there a way to re-compile just parts of gnuradio, instead of > recompiling everything? The make system will do this for you. If you change a file, it will compile only the minimum necessary set. > 0% tests passed, 1 tests failed out of 1 There currently open issues w/ ARM. I’m not sure this is one of them, but VOLK code on ARM is curently heavily under research. > How should I go about diagnosing these problems? Launch GDB and see > whats happening? Strange that this is the only test that failed. You can do that, but in general, starting with some print statements is usually more helpful (use ctest -V). I’d wait until someone from the ARM experts has had a look at this. MB ---
**Author:** ![kena](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/e9bcb4/32.png) [@kena](https://www.ruby-forum.com/u/kena)\ **Post date:** [January 22, 2014, 3:04pm UTC](https://www.ruby-forum.com/t/qa-fft-filter-make-test-failed-seg-fault/238650/3 "2014-01-22T15:04:57Z")
On Wed, Jan 22, 2014 at 4:06 AM, Martin B. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > Run ‘ctest -V -R fft\_filter’ to activate verbosity and limit the tests > > > > > There currently open issues w/ ARM. I’m not sure this is one of them, > but VOLK code on ARM is curently heavily under research. > > > How should I go about diagnosing these problems? Launch GDB and see > > whats happening? Strange that this is the only test that failed. > > You can do that, but in general, starting with some print statements is > usually more helpful (use ctest -V). I’d wait until someone from the ARM > experts has had a look at this. > > MB Also, when reporting bugs, especially on an ARM chip and with things that might be VOLK related, please tell us the version of GNU Radio you are using. If you are cloning via git, let us know the current revision. There’s work going on to address issues related to ARM and VOLK on certain platforms, so that could make a big difference. Tom