On 30/05/2016 17:38, Jim Bennett wrote: > Interesting results. The first time I ran it under control of gdb > WSJT-X started up properly. I gracefully ended it and then re-started. > Below is the output you requested. I noticed that, on the first, > successful attempt, there were six threads started after the last ALSA > warning. On the failure attempt, it died with a memory access failure > after the first thread had started. Is this indicative of a bad > Raspberry Pi card? Not having this issue anywhere else...
Hi Jim, the traceback doesn't give as much information as I thought it would, perhaps an issue with the way gdb on armhf handles interrupting a process. Just to clarify, I see a CTRL+C input on the output you reported but you said that the failed startup dies with a memory access error. Is the traceback you reported from the CTRL+C on the failed attempt? If it is, I don't understand how you know it died with a memory access error as it looks like the error did not happen until you pressed CTRL+C. BTW the memory access error is nothing to do with hardware issues, it means an instruction in the program tried to access an address that the MMU has protected i.e. reading somewhere it should not, which is a program error not a hardware error. 73 Bill G4WJS. ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
