Hi there
Just downloaded wfview and installed it on my Macbook Pro.
Every time I launch it, it crashes: 'wfview quit unexpectedly'
I have attached the generated error dump file.
I hope this is allowed to a posting (zipfile is only 20Kb in size)
73 de Robbert / PA3BKL (aka TA2IX)
wfview error dump.zip (17.6 KB)
On Sat, 8 May 2021 at 17:38, Robbert J. van Herksen<rescueteam@gmail.com> wrote: Hi there
Just downloaded wfview and installed it on my Macbook Pro.
Every time I launch it, it crashes: 'wfview quit unexpectedly'
I have attached the generated error dump file.
I hope this is allowed to a posting (zipfile is only 20Kb in size)
73 de Robbert / PA3BKL (aka TA2IX)
Hi.
We are trying to narrow-down the cause of crashing on MacOS. So far I have had reports of the latest build MacOS Test Build (2021-05-07) | wfview running successfully on Big Sur, Catalina and High Sierra, so it appears to be something specific to your environment? I wonder if you have Qt installed as it may be an older/different version to the runtime files embedded within the wfview app and for some reason these are being used instead?
73 Phil M0VSE
Build 2021-05-07 crashes on Mojave 10.14.6 as well whereas my own build runs fine.
@Phil: can you post your build environment pls ?
73 Frank
Hi Frank,
I am using Xcode 11.1 on Mac OS Big Sur. The reason for using 11.1 is that it is the last version that includes Platform API 10.15 which is the latest version supported by Qt5. The previous build was done with the latest Xcode.
It is compiled with Qt 5.15.2 and targeting MacOS v10.13 (QMAKE_MACOSX_DEPLOYMENT_TARGET = 10.13)
73 Phil M0VSE
I also release the file using macdeployqt which embeds the Qt dynamic libraries into the .app. What version of Qt do you have installed @Frank I wonder if that is where we are seeing a conflict?
73 Phil
Hi Phil,
I used this:
Xcode: Version 11.3.1 (11C505)
QT Creator: Based on Qt 5.15.2 (Clang 11.0 (Apple), 64 bit)
Did not explicitly set a target.
Build for Release.
Compiled qcustomplot stuff from source (.cpp and .h added to project)
And used macdeployqt as well, did not run on my other mac otherwise. 
73 Frank
Thatās annoying, it is almost exactly the configuration that I used for the first test build. There must be something that I am missing here? I will do some more research as we really need a build that is going to be stable on as many versions of MacOS as possible.
I donāt really want to have to generate a build for each version.
73 Phil M0VSE
@Frank Can you try:
export DYLD_PRINT_LIBRARIES=1
Before running my build of wfview.app? This should generate a list of the dynamic libraries that are being loaded and hopefully will show which one it is crashing on?
73 Phil M0VSE
Did you use libqcustomplot or used the sources? The new wfview build that crashes references the qcustomplot library.
Below my project file:
#-------------------------------------------------
#
# Project created by QtCreator 2018-05-26T16:57:32
#
#-------------------------------------------------
QT += core gui serialport network multimedia
greaterThan(QT_MAJOR_VERSION, 4): QT += widgets printsupport
TARGET = wfview
TEMPLATE = app
QMAKE_CXXFLAGS += -march=native
CONFIG(debug, release|debug) {
# For Debug builds only:
} else {
# For Release builds only:
QMAKE_CXXFLAGS += -s
QMAKE_CXXFLAGS += -fvisibility=hidden
QMAKE_CXXFLAGS += -fvisibility-inlines-hidden
QMAKE_LFLAGS += -O2 -march=native -s
}
# The following define makes your compiler emit warnings if you use
# any feature of Qt which as been marked as deprecated (the exact warnings
# depend on your compiler). Please consult the documentation of the
# deprecated API in order to know how to port your code away from it.
DEFINES += QT_DEPRECATED_WARNINGS
DEFINES += QCUSTOMPLOT_COMPILE_LIBRARY
# These defines are used for the resampler
DEFINES += OUTSIDE_SPEEX
DEFINES += RANDOM_PREFIX=wf
macx:INCLUDEPATH += /usr/local/include
macx:LIBS += -L/usr/local/lib
macx:ICON = wfview.icns
!win32:DEFINES += HOST=\\\"`hostname`\\\" UNAME=\\\"`whoami`\\\"
!win32:DEFINES += GITSHORT="\\\"$(shell git -C $$PWD rev-parse --short HEAD)\\\""
win32:INCLUDEPATH += c:/qcustomplot
win32:DEFINES += HOST=1
win32:DEFINES += UNAME=1
win32:DEFINES += GITSHORT=1
RESOURCES += qdarkstyle/style.qrc \
resources/resources.qrc
# Why doesn't this seem to do anything?
DISTFILES += resources/wfview.png \
resources/install.sh
DISTFILES += resources/wfview.desktop
linux:QMAKE_POST_LINK += cp ../wfview/resources/wfview.png .;
linux:QMAKE_POST_LINK += cp ../wfview/resources/wfview.desktop .;
linux:QMAKE_POST_LINK += cp ../wfview/resources/install.sh .;
linux:QMAKE_POST_LINK += cp -r ../wfview/qdarkstyle .;
linux:QMAKE_POST_LINK += chmod 755 install.sh;
linux:QMAKE_POST_LINK += echo; echo; echo "Run install.sh as root from the build directory to install."; echo; echo;
# Do not do this, it will hang on start:
# CONFIG(release, debug|release):DEFINES += QT_NO_DEBUG_OUTPUT
CONFIG(debug, release|debug) {
win32:QCPLIB = qcustomplotd1
else: QCPLIB = qcustomplotd
} else {
win32:QCPLIB = qcustomplot1
else: QCPLIB = qcustomplot
}
# QCPLIB = qcustomplot
#LIBS += -L./ -l$$QCPLIB
SOURCES += main.cpp\
qcustomplot.cpp \
wfmain.cpp \
commhandler.cpp \
rigcommander.cpp \
freqmemory.cpp \
rigidentities.cpp \
udphandler.cpp \
logcategories.cpp \
audiohandler.cpp \
calibrationwindow.cpp \
satellitesetup.cpp \
udpserversetup.cpp \
udpserver.cpp \
meter.cpp \
qledlabel.cpp \
pttyhandler.cpp \
resampler/resample.c \
repeatersetup.cpp \
rigctld.cpp
HEADERS += wfmain.h \
commhandler.h \
qcustomplot.h \
rigcommander.h \
freqmemory.h \
rigidentities.h \
udphandler.h \
logcategories.h \
audiohandler.h \
calibrationwindow.h \
satellitesetup.h \
udpserversetup.h \
udpserver.h \
packettypes.h \
meter.h \
qledlabel.h \
pttyhandler.h \
resampler/speex_resampler.h \
resampler/arch.h \
resampler/resample_sse.h \
repeatersetup.h \
repeaterattributes.h \
rigctld.h
FORMS += wfmain.ui \
calibrationwindow.ui \
satellitesetup.ui \
udpserversetup.ui \
repeatersetup.uiAhhh.
That might be it, I will try a build that compiles qcustomplot directly rather than using a library.
73 Phil
Copy / Paste of the wfview project file looks horrible, sorry about that.
I changed to to preformatted for you
Hi @Frank I have created a new build which contains the latest fixes and now compiles qcustomplot directly rather than using a dynamic library. MacOS Test Build (2021-05-07) | wfview (ignore the name, it is 2012-05-09 really!)
Hopefully this will cure the crashing problem?
73 Phil M0VSE
Flakey operation on my mac mini (OS 10.15.7 ) ā¦ on connection via LAN ā¦ establishes the audio path ok every time, but controls AND waterfall only worked once then froze when I changed from AM to LSB. On other attempts to run ā¦ again audio fine but often no control or waterfall. overall pretty unstable. Is there a minimum spec for Mac to run this ?
Hi John,
It āshouldā work but I have had reports of unstable operation with the latest Universal binary. Unfortunately I donāt have this problem on my Late 2013 MBP running MacOS 11.3 (Big Sur).
The problem is that the method that I used to create the Universal binary is non-standard so I have created an Intel only one using the method that I used previously that seemed more stable?
https://wfview.org/download/test-macos-build/
Please let me know how you get on with this.
73 Phil
OK, it looks like there was a bug in my new virtual serial port/pty code for Mac. It should now be fixed in the latest Intel build.
73 Phil
Hi all, I have updated the universal binary as well so I would appreciate if people could test that!
73 Phil
still fails Iām afraidā¦
Hi John,
We will need a bit more information to diagnose this the problem than āstill failsā We have had reports that the specific issue that was broken in the previous universal binary is fixed so this is likely a different problem.
What exactly is failing? Which binary did you try? Intel only or Universal? Is CI-V transceive enabled on your rig?
Can you have a look in the log file Log file | wfview and let us know what Rig: commands you see?
73 Phil M0VSE