[Kde-games-devel] ksirtet: quit with crash?

[Albert Astals Cid]

A Dimecres 12 Març 2008, Dapeng Zhang va escriure:
> Hi
>
> I'm trying to fix the "quit with crash" problem in ksirtet.
>
> starting ksirtet prints the following messages in the console
> --------------------------------------------------------------------------
> $>ksirtet
> ksirtet(10300)/kdecore (KConfigSkeleton)
> KCoreConfigSkeleton::KCoreConfigSkeleton: Creating KCoreConfigSkeleton (
> 0x80f5b10 )
> ksirtet(10300)/kdecore (KConfigSkeleton)
> KCoreConfigSkeleton::readConfig: KCoreConfigSkeleton::readConfig()
> ksirtet(10300)/kdeui (KXmlGui) KXMLGUIFactory::removeClient:
> KXMLGUIFactory::removeClient(  0x812370c  )
> ksirtet(10300)/kdeui (KXmlGui) KXMLGUIFactory::addClient:
> KXMLGUIFactory::addClient(  0x812370c  )
> ---------------------------------------------------------------------------
>
> They looks fine for me.
> However, closing ksirtet shows a crash dialog with signal 11 (SIGSEGV)
>
> ---------------------------------------------------------------------------
> KCrash: crashing... crashRecursionCounter = 2
> KCrash: Application Name = ksirtet path = <unknown> pid = 10300
> sock_file=/home/kde-devel/.kde4/socket-starkk/kdeinit4_localhost_11
> Warning: connect() failed: : No such file or directory
> KCrash cannot reach kdeinit, launching directly.
> ---------------------------------------------------------------------------
>
> I tried to play around with the destructors of some classes in "ksirtet"
> and "libksirtet" directories. But the problem still exists.
>
> Is there anyone has an idea? Which direction should I go?

Use valgrind or gdb do get more ingo about the crash.

Albert

>
> Many thanks
>
> Dapeng
> _______________________________________________
> kde-games-devel mailing list
> kde-games-devel at kde.org
> https://mail.kde.org/mailman/listinfo/kde-games-devel