Bug 264086 - Nepomuk crashed whilst updating
Summary: Nepomuk crashed whilst updating
Status: RESOLVED DUPLICATE of bug 279503
Alias: None
Product: nepomuk
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-23 15:52 UTC by Andreas Hencke
Modified: 2011-09-21 17:41 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Hencke 2011-01-23 15:52:52 UTC
Application: nepomukservicestub (0.2)
KDE Platform Version: 4.5.3 (KDE 4.5.3)
Qt Version: 4.7.0
Operating System: Linux 2.6.32-27-generic i686
Distribution: Ubuntu 10.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed:
I was updating via Muon when Nepomuk suddenly crashed. it was the second time today that Nepomuk crashed.

-- Backtrace:
Application: Nepomuk-Dienst (nepomukservicestub), signal: Segmentation fault
[Current thread is 1 (Thread 0xb78a5710 (LWP 2204))]

Thread 2 (Thread 0xb54c4b70 (LWP 2238)):
[KCrash Handler]
#7  0x002f08aa in ?? () from /lib/tls/i686/cmov/libc.so.6
#8  0x002f2afd in ?? () from /lib/tls/i686/cmov/libc.so.6
#9  0x002f4f9c in malloc () from /lib/tls/i686/cmov/libc.so.6
#10 0x0099f1dd in qMalloc (size=696) at global/qmalloc.cpp:55
#11 0x009ee20c in QString (this=0xb54c3714, size=338) at tools/qstring.cpp:1065
#12 0x009f0159 in replaceArgEscapes (s=<value optimized out>, d=..., field_width=0, arg=..., larg=..., fillChar=...) at tools/qstring.cpp:6335
#13 0x009f1ce6 in QString::arg (this=0xb54c3704, a=..., fieldWidth=0, fillChar=...) at tools/qstring.cpp:6453
#14 0x001d8eeb in Nepomuk::ResourceData::determineUri (this=0x8aebb20) at ../../nepomuk/core/resourcedata.cpp:579
#15 0x001ea383 in Nepomuk::Resource::determineFinalResourceData (this=0xb54c38e0) at ../../nepomuk/core/resource.cpp:885
#16 0x001ea622 in Nepomuk::Resource::exists (this=0xb54c38e0) at ../../nepomuk/core/resource.cpp:328
#17 0x06ca8b94 in Nepomuk::IndexScheduler::updateDir (this=0x852ed18, dir=..., analyzer=0xb54c42fc, flags=...) at ../../../../nepomuk/services/strigi/indexscheduler.cpp:345
#18 0x06ca957a in Nepomuk::IndexScheduler::updateDir (this=0x852ed18, dir=..., analyzer=0xb54c42fc, flags=) at ../../../../nepomuk/services/strigi/indexscheduler.cpp:421
#19 0x06ca957a in Nepomuk::IndexScheduler::updateDir (this=0x852ed18, dir=..., analyzer=0xb54c42fc, flags=) at ../../../../nepomuk/services/strigi/indexscheduler.cpp:421
#20 0x06ca957a in Nepomuk::IndexScheduler::updateDir (this=0x852ed18, dir=..., analyzer=0xb54c42fc, flags=) at ../../../../nepomuk/services/strigi/indexscheduler.cpp:421
#21 0x06ca957a in Nepomuk::IndexScheduler::updateDir (this=0x852ed18, dir=..., analyzer=0xb54c42fc, flags=) at ../../../../nepomuk/services/strigi/indexscheduler.cpp:421
#22 0x06ca957a in Nepomuk::IndexScheduler::updateDir (this=0x852ed18, dir=..., analyzer=0xb54c42fc, flags=) at ../../../../nepomuk/services/strigi/indexscheduler.cpp:421
#23 0x06ca957a in Nepomuk::IndexScheduler::updateDir (this=0x852ed18, dir=..., analyzer=0xb54c42fc, flags=) at ../../../../nepomuk/services/strigi/indexscheduler.cpp:421
#24 0x06cab6eb in Nepomuk::IndexScheduler::run (this=0x852ed18) at ../../../../nepomuk/services/strigi/indexscheduler.cpp:314
#25 0x009a4f39 in QThreadPrivate::start (arg=0x852ed18) at thread/qthread_unix.cpp:266
#26 0x00f7396e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#27 0x00352a4e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb78a5710 (LWP 2204)):
#0  0x00284422 in __kernel_vsyscall ()
#1  0x0035fd33 in ?? () from /lib/tls/i686/cmov/libc.so.6
#2  0x002f6697 in ?? () from /lib/tls/i686/cmov/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Possible duplicates by query: bug 214974.

Reported using DrKonqi
Comment 1 Christoph Feck 2011-01-24 03:16:59 UTC
The crash happens during allocation of memory, which indicates the memory got corrupted elsewhere. If you find a way to reproduce it, please attach a valgrind log.

For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
Comment 2 Sebastian Trueg 2011-09-21 17:41:23 UTC

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