Not a crash (yet). I removed the build tree. Did a "wsjtx build rconfig", edited the file, then "wsjtx build wsjtx".
That cmake rebuild worked though. Now on to figuring out what's going on with HRD. -----Original Message----- From: Bill Somerville [mailto:g4...@classdesign.com] Sent: Friday, September 05, 2014 5:54 PM To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] Flags On 05/09/2014 23:47, Michael Black wrote: Hi Mike, > I turned on > //Debugging option that turns on full Hamlib internal diagnostics. > WSJT_HAMLIB_TRACE:BOOL=ON > > //Leave Qt debugging statements in Release configuration. > WSJT_QDEBUG_IN_RELEASE:BOOL=ON > > //Redirect Qt debuging messages to a trace file. > WSJT_QDEBUG_TO_FILE:BOOL=ON > > //Debugging option that turns on CAT diagnostics. > WSJT_TRACE_CAT:BOOL=ON > > //Debugging option that turns on CAT diagnostics during polling. > WSJT_TRACE_CAT_POLLS:BOOL=ON > > The wsjtx_trace.log gets created but nothing goes into it. > > Do I need another flag set? No that should do it. It is conceivable that the rebuild didn't pick up the config changes, it normally does but you can force matters by making a clean build: cmake --build <build-tree-path> --target install --clean-first -- -kj Another possibility is that you are investigating a crash that happens so soon after startup that the buffer doesn't get flushed to the file. 73 Bill G4WJS. > > > From: Bill Somerville [mailto:g4...@classdesign.com] > Sent: Friday, September 05, 2014 5:14 PM > To: wsjt-devel@lists.sourceforge.net > Subject: Re: [wsjt-devel] Flags > > On 05/09/2014 23:04, Michael Black wrote: > Hi Mike, > How do we set compile flags now? > WSJT_TRACE_CAT and WSJT_QDEBUG_TO_FILE for example? > Now? This has not changed. > > Either use: > > cmake-gui <build-tree-path> > > or directly edit the CMakeCache.txt in the build tree. > > Then rebuild: > > cmake --build <build-tree-path> --target install -- -kj > > The latest JTSDK has a command to rebuild the build tree also. > > The relevant CMake options are: > > WSJT_QDEBUG_TO_FILE - causes Qt debug output to be redirected to a > file (wsjtx_trace.log in executable directory) WSJT_QDEBUG_IN_RELEASE > - causes Qt debug output to occur even in Release build configurations > WSJT_TRACE_CAT - causes WSJT_TRACE_CAT to be set to turn on extra CAT > tracing WSJT_HAMLIB_TRACE - increases the level of Hamlib tracing to > VERBOSE > > More details in CMakeLists.txt where the options and their defaults > are defined. > > > > Mike W9MDB > Hope this helps & 73 > Bill > G4WJS. > > > ---------------------------------------------------------------------- > -------- > Slashdot TV. > Video for Nerds. Stuff that matters. > http://tv.slashdot.org/ > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ---------------------------------------------------------------------------- -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ------------------------------------------------------------------------------ Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
