Bug 174071

Summary:	fecha o programa, dar uma mensgagem de erro fatal, sigabrt
Product:	[Applications] kpat	Reporter:	Arnoldo Furtado <arnoldofurtado>
Component:	general	Assignee:	Stephan Kulow <coolo>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	kde-games-bugs
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Unlisted Binaries
OS:	Other
Latest Commit:		Version Fixed In:

Description Arnoldo Furtado 2008-11-02 02:44:29 UTC

Version:           kpat (using KDE 4.1.2)
OS:                I Don't Know
Installed from:    Unspecified Linux

Aplicativo: KPaciência (kpat), sinal SIGABRT
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb52566e0 (LWP 8942)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xb80dc430 in __kernel_vsyscall ()
#7  0xb646f880 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb6471248 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb7448795 in qt_message_output () from /usr/lib/libQtCore.so.4
#10 0xb7448872 in qFatal () from /usr/lib/libQtCore.so.4
#11 0xb7448915 in qt_assert () from /usr/lib/libQtCore.so.4
#12 0x0805dc34 in _start ()
#0  0xb80dc430 in __kernel_vsyscall ()

Comment 1 Pino Toscano 2008-11-02 11:29:07 UTC

Hello Arnoldo,

unfortunately, the backtrace you posted is not useful. You can get a better one by following the instructions in the page:
http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

Also, please provide more information about how you got the crash.

Comment 2 Pino Toscano 2008-11-02 12:01:56 UTC


*** This bug has been marked as a duplicate of bug 173932 ***