On 13/07/2015 10:56, Claude Frantz wrote: Hi Claude, > On 07/12/2015 09:18 PM, John N1ISA wrote: > > Hi, > >> I am seeing a WSPR-2 segmentation fault running WSJT-X v1.6.0-devel r5717 >> in Linux. I am using a custom Ubuntu 15.04 install. I have run countless >> WSJT-X v1.6.0 devel versions without any issues for many, many months now. > In the recent past, I have encountered sporadic segmentation fault, too. > I'm not sure if this matter is related to WSPR-2. > > I'm using 32 bit Fedora 21, all available upgrades installed. > > Perhaps, we could start wsjtx under gdb, so that we can request a stack > backtrace after a failure. I ignore how to handle the treads right. Any > idea ? Always running under gdb in case of a crash isn't really necessary. Instead you can enable core dumps with whatever your system's core dump size limit command, e.g. with bash shell:
$ ulimit -c unlimited then a core dump file will get created on an unhandled exception or signal. You can get a stack trace retrospectively using gdb like this: $ gdb <original-executable> core (gdb) bt (gdb) ... This will work with release configuration executables as well although the amount of information available in gdb will be limited but a stack trace of the current thread is often enough to diagnose a crash. > > Best 88 de Claude 73 Bill G4WJS. ------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
