Re: [wsjt-devel] WSJT-X 2.0.1 Crashes on Mac 10.14.3

2019-03-05 Thread Bill Somerville

On 05/03/2019 22:04, Bill wrote:
I'm attaching another crash report taken a few days ago just in case 
it shows any new clues.


Hi Bill,

that is useful in that it is not the same crash. That probably means the 
fault is happening prior to the crash, perhaps some memory corruption, 
and the application is tripping over it later. Having said earlier that 
the diagnostic code should not be part of the problem, I now see that it 
is the problem. I have coded a fix for future releases. In the meantime 
here is a build that, correctly, does not include the offending 
diagnostic code:


https://www.dropbox.com/s/ihp37n46c8bgtj3/wsjtx-2.0.1-Darwin.dmg?dl=0

Please install it to replace your WSJT-X v2.0.1 installation and see if 
it stops the crash happening?


73
Bill
G4WJS.




___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] WSJT-X 2.0.1 Crashes on Mac 10.14.3

2019-03-05 Thread Bill Somerville

On 05/03/2019 21:15, Bill wrote:

Can someone tell me why this is happening? Invalid kernel address???

I have not seen this prior to this version.

This happens several times a week.

Thanks!

Bill - AK6A



Hi Bill,

thanks for the issue report and the crash dump. Normally macOS crash 
dumps are very useful and the issue can be easily pinpointed, in this 
case that is not so. Can you provide any other context? Does the crash 
happen only when you do something particular for example, and is it 
repeatable?


I do note from the crash dump that rig control thread was shutting down, 
that happens at application close down, when switching configurations, 
or when a critical rig control exception occurs. Do any of those 
correlate with the crash?


As an aside, which is probably unrelated, I see that some diagnostic 
code is enabled that should not be in official release builds. This will 
have a minor performance overhead and I will make a new macOS installer 
which is correctly configured - I will get Joe, K1JT, to post it on the 
project web site shortly and make an announcement that v2.0.1 macOS 
users should install the replacement version.


73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] VFO-B behavior

2019-03-05 Thread Marco Calistri
Hi Rebecca!

First of all I'd to say that I'm very pleased to meet a YL so skilled
and rich of valuable suggestions and proposals.

I agree with you both on WSJT-X usage regarding the VFO A/B behavior
which with this software could be an operator choice, as well as for the
possibility to have a separate mailing list dedicated specifically to
WSJT-X usage, in order to let the development topics free of everything
which is not strictly related to programming, despite here we have not
moderators or censors, this list is very friendly and open.

Wish you all the best and hope to have the possibility to have a QSO
with you on FT8 one of the next days.

-- 

73 de Marco, PY1ZRJ (former IK5BCU)

Il 04/03/19 21:06, Rebecca Milligan ha scritto:
> One more thought – if this group really is intended for software
> development issues, can a separate user support group be created to keep
> the programming and operator issues separate?  It could be mentioned on
> the WSJT-X webpage or in the documentation.  I think there are many who
> would volunteer to be in the group to take some of the burden off the
> developers.
> 
>  
> 
> 73,
> 
>  
> 
> N4EFS
> 
>  
> 
> *From:*Rebecca Milligan [mailto:rebeccamilli...@comcast.net]
> *Sent:* Monday, March 4, 2019 6:47 PM
> *To:* 'WSJT software development'
> *Subject:* RE: [wsjt-devel] VFO-B behavior
> 
>  
> 
> I think it would be difficult for the developers  to address every rig
> out there and every circumstance.  I consider the software a gift as I
> did not have to pay for it and I am glad to put some effort into
> experimenting and reading available documentation to see what works best
> for my situation. There are a lot of forums, posts and videos posted on
> the web by Hams discussing such topics specific to WSJT-X. 
> 
>  
> 
> The manual does address “Fake It” by basically saying each user should
> choose what works best for them:
> 
>  
> 
> /“Split Operation/: Significant advantages result from using *Split*mode
> (separate VFOs for Rx and Tx) if your radio supports it. If it does not,
> /WSJT-X/ can emulate such behavior. Either method will result in a
> cleaner transmitted signal, by keeping the Tx audio always in the range
> 1500 to 2000 Hz so that audio harmonics cannot pass through the Tx
> sideband filter. Select *Rig*to use the radio’s Split mode, or *Fake
> It*to have /WSJT-X/ adjust the VFO frequency as needed, when T/R
> switching occurs. Choose *None*if you do not wish to use split operation.”
> 
>  
> 
> “On the *Radio*tab select *Split Operation*(use either *Rig*or *Fake
> It*; you may need to experiment with both options to find one that works
> best with your radio).”
> 
>  
> 
> “Be sure that your rig control has been set up for /Split Operation/,
> using either *Rig*or *Fake It*on the *Settings | Radio*tab.”
> 
>  
> 
> It is not my intent to offend anyone.  It just seems that this group,
> which I thought was intended for software development issues, such as
> bugs in the actual software, has been steered towards answering
> questions that are addressed in the manual or problems resulting from
> operator error (clocks, notch filters, QRM, etc.)  I may have
> misunderstood the purpose of this group so I could be way off base.
> 
>  
> 
> 73,
> 
>  
> 
> Rebecca, N4EFS



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel