Hi Bill,
Did the debug build and that went fine after recompiling hamlib. Started WSJT-X
and it still hung up. SO, I started it under control of gdb. Here is the
console output result. Hope this helps identify what is happenng:
pi@raspberrypi:~/wsjtx-1.7.0/debug/bin $
pi@raspberrypi:~/wsjtx-1.7.0/debug/bin $
pi@raspberrypi:~/wsjtx-1.7.0/debug/bin $ gdb ~/wsjtx-1.7.0/debug/bin/wsjtx
GNU gdb (Raspbian 7.7.1+dfsg-5) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "arm-linux-gnueabihf".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /home/pi/wsjtx-1.7.0/debug/bin/wsjtx...done.
(gdb) r
Starting program: /home/pi/wsjtx-1.7.0/debug/bin/wsjtx
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
libEGL warning: DRI2: failed to authenticate
[New Thread 0x705fa3d0 (LWP 21016)]
[New Thread 0x6fdfa3d0 (LWP 21017)]
[New Thread 0x6f5fa3d0 (LWP 21018)]
[New Thread 0x6edfa3d0 (LWP 21019)]
[New Thread 0x6e5bc3d0 (LWP 21020)]
[New Thread 0x6ca873d0 (LWP 21021)]
[New Thread 0x6c02c3d0 (LWP 21022)]
ALSA lib pcm_dmix.c:961:(snd_pcm_dmix_open) The dmix plugin supports only
playback stream
ALSA lib pcm_dmix.c:961:(snd_pcm_dmix_open) The dmix plugin supports only
playback stream
ALSA lib pcm_dmix.c:961:(snd_pcm_dmix_open) The dmix plugin supports only
playback stream
ALSA lib pcm_dsnoop.c:557:(snd_pcm_dsnoop_open) The dsnoop plugin supports only
capture stream
ALSA lib pcm_dsnoop.c:557:(snd_pcm_dsnoop_open) The dsnoop plugin supports only
capture stream
ALSA lib pcm_dsnoop.c:557:(snd_pcm_dsnoop_open) The dsnoop plugin supports only
capture stream
ALSA lib pcm_dsnoop.c:557:(snd_pcm_dsnoop_open) The dsnoop plugin supports only
capture stream
ALSA lib pcm_dsnoop.c:557:(snd_pcm_dsnoop_open) The dsnoop plugin supports only
capture stream
[New Thread 0x675bc3d0 (LWP 21023)]
^C
Program received signal SIGINT, Interrupt.
0x75b23578 in __divsi3 () from /lib/arm-linux-gnueabihf/libgcc_s.so.1
(gdb) info threads
Id Target Id Frame
9 Thread 0x675bc3d0 (LWP 21023) "QThread" 0x75a74c80 in poll () at
../sysdeps/unix/syscall-template.S:81
8 Thread 0x6c02c3d0 (LWP 21022) "threaded-ml" 0x75a74c80 in poll () at
../sysdeps/unix/syscall-template.S:81
7 Thread 0x6ca873d0 (LWP 21021) "Qt bearer threa" 0x75a74c80 in poll () at
../sysdeps/unix/syscall-template.S:81
6 Thread 0x6e5bc3d0 (LWP 21020) "QXcbEventReader" 0x75a74c80 in poll () at
../sysdeps/unix/syscall-template.S:81
5 Thread 0x6edfa3d0 (LWP 21019) "llvmpipe-3" 0x75af97a4 in
__pthread_cond_wait (cond=0x43a6fc0, mutex=0x43a6fa8)
at pthread_cond_wait.c:187
4 Thread 0x6f5fa3d0 (LWP 21018) "llvmpipe-2" 0x75af97a4 in
__pthread_cond_wait (cond=0x43a6eb0, mutex=0x43a6e98)
at pthread_cond_wait.c:187
3 Thread 0x6fdfa3d0 (LWP 21017) "llvmpipe-1" 0x75af97a4 in
__pthread_cond_wait (cond=0x43a6da0, mutex=0x43a6d88)
at pthread_cond_wait.c:187
2 Thread 0x705fa3d0 (LWP 21016) "llvmpipe-0" 0x75af97a4 in
__pthread_cond_wait (cond=0x43a6c90, mutex=0x43a6c78)
at pthread_cond_wait.c:187
* 1 Thread 0x735f9000 (LWP 21013) "wsjtx" 0x75b23578 in __divsi3 () from
/lib/arm-linux-gnueabihf/libgcc_s.so.1
(gdb) bt
#0 0x75b23578 in __divsi3 () from /lib/arm-linux-gnueabihf/libgcc_s.so.1
#1 0x75b23778 in __aeabi_idivmod () from /lib/arm-linux-gnueabihf/libgcc_s.so.1
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) q
A debugging session is active.
Inferior 1 [process 21013] will be killed.
Quit anyway? (y or n) y
pi@raspberrypi:~/wsjtx-1.7.0/debug/bin $
On Monday, May 30, 2016 4:04 PM, Bill Somerville <[email protected]>
wrote:
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
------------------------------------------------------------------------------
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
