On 14/03/2016 16:19, Clemens Heese wrote: > At least I get a segmentation fault with all my wav files, which decode fine > on my other machines. > Let me know how I can configure a debug build and I will distribute the > output. Hi Clemens,
assuming you are building WSJT-X using CMake then you will need to create a separate build for the debug configuration build. So for example if you configured a default release configuration build something like: mkdir -p ~/wsjtx-prefix/build cd ~/wsjtx-prefix/build cmake ... -D CMAKE-INSTALL_PREFIX=~/wsjtx-prefix ~/wsjtx-prefix/src cmake --build . --target install then to make a debug configuration build you would do the above again with the following additions: mkdir -p ~/wsjtx-prefix/build/Debug cd ~/wsjtx-prefix/build/Debug cmake ... -D CMAKE_BUILD_TYPE=Debug -D CMAKE_INSTALL_PREFIX=~/wsjtx-prefix/Debug ~/wsjtx-prefix/src cmake --build . --target wsprd this will build the wsprd program in a debug configuration located in the current directory. As a first step run the debug version using gdb on the target machine like: gdb --args wsprd -f 7.0386 wspr_7038600160310_1944.wav ... (gdb) start the program with the 'r' command and when the SEGV happens you can get a stack backtrace by using the 'bt' command. Send us the output of that and I will assess what the best next step is. 73 Bill G4WJS. ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140 _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
