On 30/05/2016 19:03, Jim Bennett wrote:
> I probably mis-interpreted the output of the traceback; saw the memory
> access error and ässumed" it was what caused the program to not
> complete initialization. So, next steps?
Hi Jim,
let's try a debug build. To do that you are probably best to create a
second build tree and keep the release configuration tree for release
builds. So create a new build directory, something like:
mkdir ~/wsjtx-prefix/build/debug
then change working directory to it and configure the build. The
difference in the configure is that you must set CMAKE_BUILD_TYPE=Debug
and set a different CMAKE_INSTALL_PREFIX so that the Debug build gets
installed in a different place from the release configuration install.
Something like:
cd ~/wsjtx-prefix/build/debug
cmake -D CMAKE_BUILD_TYPE=Debug \
-D CMAKE_INSTALL_PREFIX=~/wsjtx-prefix/debug \
-D CMAKE_PREFIX_PATH=~/hamlib-prefix \
-D WSJT_GENERATE_DOCS=OFF \
~/wsjtx-prefix/src
cmake --build . --target install -- -j2
Adjust paths above to suit your installation. Once the build is complete
you can test the debug build like:
~/wsjtx-prefix/debug/bin/wsjtx
If it hangs in the same way try running it under gdb and using CTRL+C to
break in, then interrogate the threads and current thread back trace as
before:
gdb ~/wsjtx-prefix/debug/bin/wsjtx
(gdb) r
... program hangs ...
^C
(gdb) info threads
... prints threads ...
(gdb) bt
... prints current thread stack back trace ...
(gdb) q
There should be much more information in the stack back trace from the
debug configuration build.
73
Bill
G4WJS.
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
