Thanks Josh, I agree that each wsjtx-jt9 pair needs a separate shared
memory region. If you choose to do the modest number of code changes,
let me know. I'll be happy to add them to the code base.
-- Joe, K1JT
On 7/15/2013 1:15 PM, Josh Rovero wrote:
The issue is almost certainly the use of a single QSharedMemory key,
"mem_jt9", line 10 of "main.cpp". Each paired wsjt-x& jt9 need to share a
key, but the other pairs running on the same machine need different keys.
Otherwise, there is a stompfest in the single shared memory area.
It might be practical to use a command line option to pass a string to
modify the key. The security folks would prefer dynamically generated,
difficult to guess keys. Otherwise, someone will be writing shared memory
malware targeted at the application.
_______________________________________________
Wsjt-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/wsjt-devel
