On 10/11/2015 06:28, Claude Frantz wrote: > Hi all, Hi Claude, > > Yesterday, I have encountered an error situation with wsjtx, where the > waterfall window was frozen and the main window was running partially > only. I confess that I was unable to get useful information about the > encountered situation, which could be useful for debugging. I'm using > the source code compiled locally with 32 bit Fedora Linux. > > Please give me your opinion about a recommended procedure to handle such > situations, in order to get useful debugging information for the > developers. How can I use gdb in the wsjtx environment ? What can I do > if errors occur ? > > Many thanks to you. The Qt framework uses a single event loop for all activity in the main thread, that includes all UI activity. Because of this it is very unlikely that the behaviour you describe is anything more than a programming error in the application. To diagnose such an issue requires a reasonable knowledge of the program logic, at least in the area of the UI related to the issue. There is no substitute to studying the source code and learning the Qt framework class interfaces and usage.
If you are not comfortable with diagnosing issues yourself at tye source code level, and we certainly do not expect all on this list to be able to do that, then the most useful contribution is a recipe for reproducing the issue with as few steps as possible. It is important when reporting such a recipe to reproduce an issue that start conditions are included. For example it is not helpful to say something like "the attached .WAV file causes the screen to freeze" without saying what mode the application was set to decode. > > Best 88 de Claude (DJ0OT) 73 Bill G4WJS. ------------------------------------------------------------------------------ _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
