kprint segfault, gdb files

[Matthias Posseldt]

On Saturday 29 March 2003 16:15, Michael W. Holdeman wrote:
> Here are some backtraces from 2 seperate kdeprint puking episodes. It now
> won't print at all using kprint. Other apps (OO) print using cups just
> fine..

Sorry, but those backtraces don't help at all, because you have compiled 
kdeprint with full optimization and it removed all symbols. A normal -O2 
-march=pentium3 -pipe compilation doesn't remove all symbols so that you get 
some information from these backtraces, as in the backtrace provided with the 
bug #56263 (http://bugs.kde.org/show_bug.cgi?id=56263). There you can see 
which functions were called and where the signal handler was called.

Ciao, Matthias

-- 
"If liberty means anything at all,
it means the right to tell people
what they do not want to hear."

George Orwell