Re: [Hamlib-developer] On toward 4.6

[Black M. <mdb...@ya...>]

I just put a heavier LOCK() around the send_morse loop.  See if behaves better now.








On Sunday, December 1, 2024 at 02:27:03 PM CST, George Baltz <geo...@gm...> wrote: 





I found one problem last weekend in the CQWW CW contest - CW sending is 
very unreliable (random failures, timeouts, duplicate messages, delays) 
and even lockups requiring restart of the logging program(tlf),  I've 
been looking at the code, and it looks to me like a thread safety 
problem.  Happens only when the app mixes CW sending with polling for 
freq/mode.

I've found ways to make it better, but not sure of a complete fix.


On 12/1/24 1:04 PM, Nate Bargmann wrote:
> Hi All.
>
> Mike has let me know that he is confident that Hamlib is very close to
> the 4.6 release.  If anyone has any outstanding patches to include, now
> is the time to submit them!  Anything such as spelling/grammar
> corrections and documentation improvements are welcome at this time as
> well.
>
> On my end I've updated my virtual machine to the latest Debian 11 (I like
> to run a release behind on builds just to be sure things work across at
> least a few years worth of build tooling) and will be doing some mock
> releases I can test on Debian 12 and Arch.  Around the end of this week
> I plan to create the 4.6 branch and make an RC archive that I'll host at
> the daily snapshots page.
>
> Ordinarily I wouldn't be quite so cautious but since it has been some
> time since the last release, I'd like to "shake the bushes" so to speak
> before 4.6.
>
> 73, Nate
>
>
>
> _______________________________________________
> Hamlib-developer mailing list
> Ham...@li...
> https://lists.sourceforge.net/lists/listinfo/hamlib-developer



_______________________________________________
Hamlib-developer mailing list
Ham...@li...
https://lists.sourceforge.net/lists/listinfo/hamlib-developer