[Kst]
[Bug 64977] crash - no user input, no new data, full on kst crash
George Staikos
staikos at kde.org
Fri Sep 26 15:32:22 CEST 2003
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=64977
------- Additional Comments From staikos at kde.org 2003-09-26 15:32 -------
Subject: Re: [Kst] New: crash - no user input, no new data, full on kst crash
On Friday 26 September 2003 04:22, Matthew Truch wrote:
> Backtrace as below.
>
> No user input to kst (it was in another virtual desktop) at the time of the
> crash. There was no live data coming into kst, in fact, blastcom may have
> been restarted when it happened (exact timing unknown).
>
> There were 3 other kst's running, which did not crash.
>
> I'm sorry I don't know any more.
>
> [New Thread 1098147776 (LWP 2840)]
> 0xffffe002 in ?? ()
> #0 0xffffe002 in ?? ()
> #1 0x406c957d in KCrash::defaultCrashHandler(int) ()
> from /usr/lib/libkdecore.so.4
> #2 <signal handler called>
> #3 0x0805d026 in GetNFrames ()
> #4 0x080a0b58 in KstFile::dirfileUpdate() ()
Can you recompile with debug? Run ./configure --enable-debug
--prefix=/wherever , make clean, make install. Then the backtrace will have
more information. This could be related to my fix for the disappearing
KstFiles, but without a line number it's hard to know exactly what went
wrong.
More information about the Kst
mailing list