Need external opinion about backtrace

[Roger Larsson]

On Wednesday 06 November 2002 14.35, Michael Goffioul wrote:
> I received a bug report about kprinter crashing with Alarm clock
> signal. The backtrace is below. I doubt the bug lies in kdeprint's
> code as the crash occurs somewhere else. I'm wondering about the
> compiler (2.95.3). Any opinion?
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x40840a1c in free () from /usr/kde/3.1/lib/libkdecore.so.4
> (gdb) bt
> - - - deleted - - -

These kinds of crashes might be due to a pointer error / accessing a deleted 
object ... the problem can start much higher up in the call chain than 
expected. If this was from RC1 it might be related to a qt bug that fired 
timed events too early. See Bug #49896

/RogerL

-- 
Roger Larsson
Skellefteå
Sweden