Joe, Yes, I am building on a 64-bit system: $ arch x86_64 It crashes on both files on r5830. Also - my earlier assertion that adding write and printf statements cured the crash on one of the files was incorrect. I was testing the wrong file. Both files consistently crash r5829 and r5830.
Do you think that the presence of different nhash.c’s in src/lib and in src/lib/wsprd could be causing problems? It does seem that if that was a problem, then you and others would be seeing the crashes… Steve k9an > On Aug 30, 2015, at 1:17 AM, Joe Taylor <j...@princeton.edu> wrote: > > Steve -- > > Are you building on a 64-bit system? Anyway, please try compiling > revision 5830. I changed line 204 in nhash.c so as to force the second > argument to be a 32-bit unsigned (rather than "size_t") integer. > > -- Joe, K1JT > > On 8/29/2015 7:45 PM, Steven Franke wrote: >> The crash is occuring at the call to nhash in syncmsk.f90. It acts like a >> memory access error because adding a bunch of write(*,*) and printf() >> statements “cured" the crash on one of the files. It still happens on the >> second file. A print statement at the beginning of the wrapper function >> nhash_() is not executed - so the problem appears to be something associated >> with the fortran-c interface. >> >> Steve k9an >> >> >>> On Aug 29, 2015, at 10:45 PM, Joe Taylor<j...@princeton.edu> wrote: >>> >>> Hi Steve, >>> >>> Thanks for the files. Neither one makes the program crash for me with >>> r5829 in either Windows or Linux, so I'm presently at a loss to offer >>> any diagnosis. >>> >>> -- Joe >>> >>> On 8/29/2015 5:23 PM, Steven Franke wrote: >>>> Joe, >>>> >>>> Here is yet another try at sending links to files that crash the current >>>> 1.6.1 jtmsk: >>>> >>>> https://www.dropbox.com/s/yy1k7wzrfb1ppeu/150829_144945.wav?dl=0 >>>> >>>> https://www.dropbox.com/s/jyrfa7qgfgsgt3w/150829_202100.wav?dl=0 >>>> >>>> Previously, I tried to send the links that are generated when I >>>> right-click on a file in the local copy of the Public folder in Dropbox. >>>> This is how I’ve always done it in the past - but that latest incarnation >>>> of Mail.app silently refuses to send files that contain that type of link. >>>> >>>> Steve k9an >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> _______________________________________________ >>>> wsjt-devel mailing list >>>> wsjt-devel@lists.sourceforge.net >>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >>> >>> ------------------------------------------------------------------------------ >>> _______________________________________________ >>> wsjt-devel mailing list >>> wsjt-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel >> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> wsjt-devel mailing list >> wsjt-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > ------------------------------------------------------------------------------ > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ------------------------------------------------------------------------------ _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
