Bug 245700 - Kpat application crashes seems traceback not in use
Summary: Kpat application crashes seems traceback not in use
Status: RESOLVED WORKSFORME
Alias: None
Product: kpat
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Stephan Kulow
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2010-07-25 03:18 UTC by trelcr
Modified: 2018-10-21 04:45 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Is a snapshot of detailed report in jpeg format (149.14 KB, image/jpeg)
2010-07-25 03:18 UTC, trelcr
Details

Note You need to log in before you can comment on or make changes to this bug.
Description trelcr 2010-07-25 03:18:42 UTC
Created attachment 49470 [details]
Is a snapshot of detailed report in jpeg format

Version:           unspecified (using KDE 1.2) 
OS:                Linux



Reproducible: Couldn't Reproduce




Processor (CPU):   Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz
  Speed:  1,197.00 MHz
  Cores:  4
Total memory (RAM):  7.8 GB
  Free memory:  5.9 GB (+ 1.4 GB Caches)
  Free swap:  2.0 GB
Filesystem
Total space        Available space
 /  ext3  914.9 GB  622.6 GB
OS:  Linux 2.6.27.48-0.1-default x86_64
  System:  openSUSE 11.1 (x86_64)
  KDE:  4.1.3 (KDE 4.1.3) "release 4.11.1"
Comment 1 Christoph Feck 2010-07-26 15:02:06 UTC
If you can reproduce, please attach a complete backtrace as a text file, not only a part of it as an image. See http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
Comment 2 trelcr 2010-07-28 23:46:51 UTC
Hi Cristoph,

KPatiance was the only one application that was running in the time. In this
time the thing is repeated so I can attach tho whole bug report:

 This backtrace appears to be of no use.

This is probably because your packages are built in a way which prevents
creation of proper backtraces, or the stack frame was seriously corrupted in
the crash.

[?1034h(no debugging symbols found)

(no debugging symbols found)

(no debugging symbols found)

[Thread debugging using libthread_db enabled]

(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)

(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)

0x00007fcb56fcdcf1 in nanosleep () from /lib64/libc.so.6

[Current thread is 1 (Thread 0x7fcb5d8ce750 (LWP 4663))]

Thread 1 (Thread 0x7fcb5d8ce750 (LWP 4663)):

#0 0x00007fcb56fcdcf1 in nanosleep () from /lib64/libc.so.6

#1 0x00007fcb56fcdaec in sleep () from /lib64/libc.so.6

#2 0x00007fcb5c91954f in ?? () from /usr/lib64/libkdeui.so.5

#3 0x00007fcb5c919eaa in KCrash::defaultCrashHandler(int) () from
/usr/lib64/libkdeui.so.5

#4 <signal handler called>

#5 0x00007fcb56f5e645 in raise () from /lib64/libc.so.6

#6 0x00007fcb56f5fc33 in abort () from /lib64/libc.so.6

#7 0x00007fcb56f9a8e8 in ?? () from /lib64/libc.so.6

#8 0x00007fcb56fa0108 in ?? () from /lib64/libc.so.6

#9 0x00007fcb5c9b6c85 in ?? () from /usr/lib64/libkdeui.so.5

#10 0x00007fcb5c9b6ba1 in ?? () from /usr/lib64/libkdeui.so.5

#11 0x00007fcb5c9b6ba1 in ?? () from /usr/lib64/libkdeui.so.5

#12 0x00007fcb5c9b48e3 in KXMLGUIFactory::~KXMLGUIFactory() () from
/usr/lib64/libkdeui.so.5

#13 0x00007fcb5d419941 in QObjectPrivate::deleteChildren() () from
/usr/lib64/libQtCore.so.4

#14 0x00007fcb57e4c72d in QWidget::~QWidget() () from
/usr/lib64/libQtGui.so.4

#15 0x00007fcb5c970ff6 in KMainWindow::~KMainWindow() () from
/usr/lib64/libkdeui.so.5

#16 0x00000000004279f3 in _start ()


Best regards.

george


2010/7/26 Christoph Feck <christoph@maxiom.de>

> https://bugs.kde.org/show_bug.cgi?id=245700
>
>
> Christoph Feck <christoph@maxiom.de> changed:
>
>           What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>             Status|UNCONFIRMED                 |NEEDSINFO
>                 CC|                            |kde-games-bugs@kde.org
>          Component|general                     |general
>         Resolution|                            |BACKTRACE
>         AssignedTo|unassigned-bugs@kde.org     |coolo@kde.org
>            Product|kde                         |kpat
>
>
>
>
> --- Comment #1 from Christoph Feck <christoph maxiom de>  2010-07-26
> 15:02:06 ---
> If you can reproduce, please attach a complete backtrace as a text file,
> not
> only a part of it as an image. See
>
> http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
>
> --
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
>
Comment 3 Andrew Crouthamel 2018-09-20 22:08:45 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-10-21 04:45:24 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!