This isn't a code problem. jpilot 1.8.1 is supported on Slackware 14.2. If you are experiencing problems that others are unable to reproduce then this means the problem is isolated to your slackware installation, NOT the program itself. The jpilot devs cannot help you if they are unable to reproduce the problem.
Check version numbers and dependencies. It's possible that you have installed a different version of a dependency that is throwing it off. - what version of jpilot are you building? - have you modified any of the slackware packages or config files jpilot depends on? Use ldd to find the libraries jpilot is linked too. $ ldd `which jpilot` And compare accordingly. If you need to, use a clean install of slackware to verify that it works. I know you have a tendency to modify your env variables so something is probably just out of alignment. On Fri, Aug 2, 2019 at 8:16 AM Johnathan Mantey <[email protected]> wrote: > Use gdb on the core file to find out where it died? > > On Fri, Aug 2, 2019 at 8:07 AM Rich Shepard <[email protected]> > 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 > > [email protected] > > http://lists.pdxlinux.org/mailman/listinfo/plug > > > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
