Actually, run gdb on jpilot and get at least a stack trace, better if you can get it to dump core. then you can provide the trace/core to the devs for further analysis.
> On Aug 2, 2019, at 10:15 AM, Johnathan Mantey <mante...@gmail.com> wrote: > > Use gdb on the core file to find out where it died? > > On Fri, Aug 2, 2019 at 8:07 AM Rich Shepard <rshep...@appl-ecosys.com> > wrote: > >> On Fri, 2 Aug 2019, Ken Stephens wrote: >>> Have you ever used strace on the program. You might be able to find where >>> if segfaults. >> >> Ken, >> >> Yes, I should have mentioned that. Strace did not reveal where or why it >> segfauts. >> >> Thanks, >> >> Rich >> _______________________________________________ >> PLUG mailing list >> PLUG@pdxlinux.org >> http://lists.pdxlinux.org/mailman/listinfo/plug >> > _______________________________________________ > PLUG mailing list > PLUG@pdxlinux.org > http://lists.pdxlinux.org/mailman/listinfo/plug -- Louis Kowolowski lou...@cryptomonkeys.org <mailto:lou...@cryptomonkeys.org> Cryptomonkeys: http://www.cryptomonkeys.com/ <http://www.cryptomonkeys.com/> Making life more interesting for people since 1977 _______________________________________________ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
