On Sun, Oct 18, 2015 at 09:59:00PM -0600, Greg Beam wrote:
Build it and enable the Debug options, then run it with GDB.
I've tested v1.5.0, 1.6.0 adn v1.6.1, and have yet to get a Segfault. Can
you detail exactly how you installed and run v1.5.0?
This is the version currently in Debian. Version 1.1.r3496-3.
I just installed it from the archives.
With the current packaging method, "It Can't" be carried by Debian, as it's
using a Custom Static version of Hamlib. This issue will be resolved in the
not to distant future.
Additionally, KVASD ( the non-FOSS decoder) is about to be replaced by a
complete Open Source Decoder, with equal performance.
Ok yes, I came across these issues. I'm glad they're being worked on.
As everyone knows, Launchpad is not for Debian, I get reminded of this all
the time when I even mention word "Launchpad" in Debian arenas. I can say,
for certain, there's not problems with 1.5.0, 1.6.0 or 1.6.1 branches on
Ubuntu Trusty, Vivid or Wily. And, I don't recall any faults of the three
branches on Jessie, for what it's worth.
Yep, ok. So we know things are working in Ubuntu but there are DFSG issues
to resolve before the Debian package can be updated. That's the information
I was looking for.
A Couple of things to note:
[1] I've not looked recently, but I believe Nate (the Hamlib developer)
release version 3.0 or there about. At some point, WSJT-X will start to use
the distribution of Hamlib rather than a customer static library. There's no
sense in trying to package this any further until that happens.
I guess I should probably get round to packaging the new hamlib then.
Version 3.0 has been released.
[2] WSJT-X still relies on KVASD, the non-FOSS decoder, however, the
upstream team is about to release a FOSS decoder that is equal too or better
than KVASD, so, again, no point in pressing ahead until this happens as
WSJT-X, without the KVASD binary is severely degraded. However, you can use
the utility package ( PPA: kvasd-installer ) to install the decoder after
installing WSJT-X.
Ok cool. (:
http://anonscm.debian.org/cgit/pkg-hamradio/wsjtx.git
I'll have a look at the info and see if there is anything obvious I can
detect.
It's probably not worth taking a look, as if there are DFSG issues that
you're working on and you understand the package better than me, you should
probably throw that git repo away and just work from what you have.
One thing to note though, is that the source I downloaded for 1.5.0 seemed
to contain two tarballs, one for the hamlib and one for wsjtx. The FTP team
will not allow sources to be shipped in tarballs inside source packages as
it interferes with things like sources.debian.net. Source code in the
package must be in the "preferred form of editing". See:
https://wiki.debian.org/UnpackWaf
Thanks for your work on this.
Iain.