You should be using Thrift 0.9.3 release, and configure thrift to be single threaded (how escapes me at the moment.)
Johnathan Corgan Corgan Labs - SDR Training and Development Services http://corganlabs.com On Wed, Aug 24, 2016 at 1:51 PM, Harper, Andrew < [email protected]> wrote: > > Hi, I am having trouble installing Control Port, and I'm hoping someone > can point me in the right direction. I've been following the directions > here: > > http://gnuradio.org/redmine/projects/gnuradio/wiki/ > ControlPort#Thrift-092-Shutdown-Patch > > > I set the PYTHONPATH to: > > ~/thrift$ export PYTHONPATH=$PYTHONPATH:/usr/ > lib/python2.7/site-packages > > > and defined the prefix: > > ~/thrift$ export prefix=/usr > > > and changed the appropriate files to implement the patch as shown in: > > source:gnuradio-runtime/lib/controlport/thrift/thrift- > codebase-shutdown-patch.diff > <http://gnuradio.org/redmine/projects/gnuradio/repository/entry/gnuradio-runtime/lib/controlport/thrift/thrift-codebase-shutdown-patch.diff> > > > and in the configure step used: > ~/thrift$ ./configure --prefix=$prefix \ > --with-c_glib --with-cpp --with-libevent --with-python \ > --without-csharp --without-d --without-erlang --without-go \ > --without-haskell --without-java --without-lua --without-nodejs \ > --without-perl --without-php --without-ruby --without-zlib \ > --without-qt4 --without-qt5 \ > --disable-tests --disable-tutorial $config_opt \ > CC=$cc CXX=$cxx PY_PREFIX=$prefix CXXFLAGS="-DNDEBUG" > > > The Thrift install seems to work and GNU Radio recognizes that it's > enabled: > > ~/gnuradio/build$ thrift --version > Thrift version 0.9.2 > > > -- ###################################################### > -- # Gnuradio enabled components > -- ###################################################### > -- * python-support > -- * testing-support > -- * volk > -- * doxygen > -- * gnuradio-runtime > -- * gr-ctrlport > -- * * thrift > > > But when I run ctest and output to file I see errors due to segfaults. > Here is an example where I run ctest twice in a row: > > ~/gnuradio/build$ ctest -j4 --output-on-failure > ctestout.txt > Errors while running CTest > ~/gnuradio/build$ ctest -j4 --output-on-failure > ctestout2.txt > Errors while running CTest > > > Here are a few failure messages from the first file: > > ~/gnuradio/build$ vim ctestout.txt > > > > 17/211 Test #45: qa_ctrlport_probes ...................***Failed > 1.60 sec > INFO: Apache Thrift: -h swarm-nuc05 -p 40196 > ..... > ------------------------------------------------------------ > ---------- > Ran 5 tests in 0.513s > OK > Segmentation fault (core dumped) > > 33/211 Test #194: qa_qtgui .............................***Failed > 1.29 sec > > ............ > ------------------------------------------------------------ > ---------- > Ran 12 tests in 0.282s > OK > Segmentation fault (core dumped) > > > > The following tests FAILED: > 7 - qa_kludged_imports (Failed) > 34 - qa_vector_insert (Failed) > 45 - qa_ctrlport_probes (Failed) > 194 - qa_qtgui (Failed) > > > And a few from the second file: > > ~/gnuradio/build$ vim ctestout2.txt > > > > 111/211 Test #130: qa_sig_source ........................***Failed > 0.73 sec > ........... > ----------------------------------------------------------- > ----------- > Ran 11 tests in 0.015s > OK > Segmentation fault (core dumped) > > 187/211 Test #97: qa_goertzel ..........................***Failed > 0.43 sec > .. > ------------------------------------------------------------ > ---------- > Ran 2 tests in 0.008s > OK > Segmentation fault (core dumped) > > The following tests FAILED: > 15 - qa_bin_statistics (Failed) > 74 - qa_vector_sink_source (Failed) > 97 - qa_goertzel (Failed) > 130 - qa_sig_source (Failed) > > > As you can see, each time I run ctest a new set of tests fail. It seems to > be completely random. I have tried everything I can thing of based on the > installation instructions. Has anyone else had this issue when installing > Control Port? There haven't been many posts about Control Port recently, is > it even supported anymore? Is there an alternative method of looking into > which blocks are causing bottlenecks in GNU Radio? > > > Thanks for your help, > > > Andrew Harper > > Information and Communications Lab (ICL) > > Georgia Tech Research Institute > > > > > > _______________________________________________ > Discuss-gnuradio mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio > >
_______________________________________________ Discuss-gnuradio mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
