On Thu, 2023-07-06 at 01:24 -0700, dchme...@gmail.com wrote: > On 9/8/22 6:07 AM, Dominique Dumont wrote: > > On Thursday, 8 September 2022 12:16:10 CEST David Chmelik wrote: > > > I compiled pan 0.151 but, after starting, quickly got another > > > segmentation fault. > > Can you get a backtrace? [...] > > Now I compiled 0.154. I don't know that I'll be able to get a > backtrace. Do I need debugging compiled in, and if so, how do I do > that > then get the backtrace?
Hi, I don't use and compile pan any more, so my advice is very generic as old school guys do. Pan code is c++, so it can be debugged by gdb. Look gdb manual how to use it. Basic case is "gdb <program>", where <program is compiled pan. Pan should be compiled for debugging, which means that source code is added, so when pan crashes, you get line info where in code it does so. For testing your need a test case. In test case the is a list of steps described how to reach the problem. -- Reijo Korhonen, old school developer > _______________________________________________ > Pan-users mailing list > Pan-users@nongnu.org > https://lists.nongnu.org/mailman/listinfo/pan-users _______________________________________________ Pan-users mailing list Pan-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/pan-users
