From: geier (geierwally_at_gmx.net)
Date: Wed Jul 13 2005 - 16:51:58 CEST
From: geier <geierwally@gmx.net> Message-Id: <20050713145158.B90CE272E928@einstein.suse.de> Date: Wed, 13 Jul 2005 16:51:58 +0200 (CEST) Subject: [taskjuggler-devel] Crash in taskjuggler
Hello Chris,
I don't know if this is a topic of TJ or kde, but just for short I'd like to let yo know about a reproducable crash scenario in TaskJuggler I currently don't have time to investigate:
When I have a project loaded (w/o errors) and inserting an error condition by editing the source (incomplete task, no start point), then trying to show a report (e.g. for looking up a date value) produces a SEGV in the svn version. Is this a known/common issue?
If some spare time comes, I'd like to have a closer look at this. Here's the info of KDE crash manager for short:
Using host libthread_db library "/lib/tls/libthread_db.so.1".
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1234393408 (LWP 14023)]
0xffffe410 in __kernel_vsyscall ()
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb6e14613 in waitpid () from /lib/tls/libc.so.6
#2 0xb77a0deb in KCrash::defaultCrashHandler ()
from /usr/kde/3.4/lib/libkdecore.so.4
#3 0xb7ea0d92 in ?? () from /usr/kde/3.4/lib/libtaskjuggler.so.1
#4 0xb7e9ade1 in ?? () from /usr/kde/3.4/lib/libtaskjuggler.so.1
#5 0xb749a5c8 in QString::deref () from /usr/qt/3/lib/libqt-mt.so.3
Kind regards!
Eckard
-- To unsubscribe, email: taskjuggler-devel-unsubscribe@suse.com For additional commands, email: taskjuggler-devel-help@suse.com
This archive was generated by hypermail 2.1.7 : Wed Jul 13 2005 - 16:52:06 CEST