On Tue, 2023-07-11 at 18:56 -0700, David Chmelik wrote:
Well, how do I do that? This command had no output: ./configure
--help|grep -i debug .
My answer is again very generic.
Hmm... Is your target to debug pan. What your have done before? If you
run "./configure", this command is normally run, when you have
downloaded on application zip-package and unzipped it gone to unzipped
app-code main directory. There is little runnable script ""configure".
"configure" makes makefiles for your system. After "./configure" your
compile pan with a command "make" in same directory, where your run
"./configure".
Google "linux compile debuggeble" and you get basics, for instance "
https://newton.ex.ac.uk/teaching/resources/software/linuxcc/";
When you have run ./configure, you have got makefile for compiling pan.
"./configure" (without grep) hopefully tells how you can confugure what
kind makefile is generated. But you can edit makefile yourself and as
Google tells us, your can edit makefile for generating debuggable
runnable by hand. Check that compiling flags include "-Oo -g", meaning
no optimazion and runnable will include code information", so when you
debug pan, your get code lines where runnable fails.
When you run gdb <path to runnable-pan> your propably should be in same
directory, where you run "make", so gdb can find pan code lines. [...]