Bug 142340 - Crash after start in QMapPrivate
Summary: Crash after start in QMapPrivate
Status: RESOLVED WORKSFORME
Alias: None
Product: knotes
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: Michael Brade
URL:
Keywords:
: 146840 147023 147025 147085 147337 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-02-28 19:38 UTC by Robert Gomułka
Modified: 2009-06-04 21:07 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Gomułka 2007-02-28 19:38:31 UTC
Version:            (using KDE KDE 3.5.6)
Installed from:    Debian testing/unstable Packages
OS:                Linux

I pressed alt-f2 to run command in KDE. I entered knotes and pressed enter. Instead of knotes window I got KDE crash handler with the following output:
(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(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 -1237518640 (LWP 4134)]
(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]
#5  0xb7f132e7 in QMapPrivate<QCString, QString>::find ()
   from /usr/lib/libkcal.so.2
#6  0xb7eac1f9 in KCal::CustomProperties::nonKDECustomProperty ()
   from /usr/lib/libkcal.so.2
#7  0xb7eac2fb in KCal::CustomProperties::customProperty ()
   from /usr/lib/libkcal.so.2
#8  0x0807709f in ?? ()
#9  0xbfba6c50 in ?? ()
#10 0x08187d7c in ?? ()
#11 0xbfba6bc0 in ?? ()
#12 0xbfba6bb8 in ?? ()
#13 0xfffffff6 in ?? ()
#14 0x00000010 in ?? ()
#15 0x00000010 in ?? ()
#16 0x00000000 in ?? ()

I reproduced it three times in a row, when running both from alt-f2 and konsole.
Comment 1 Bram Schoenmakers 2007-03-02 20:27:46 UTC
Please install kdepim-dbg, kdebase-dbg and kdelibs-dbg and try to reproduce and post the backtrace here. There's not much we can do at this point.
Comment 2 Robert Gomułka 2007-03-02 22:28:46 UTC
You're welcome - I like helping :)
(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1237219632 (LWP 6501)]
[KCrash handler]
#5  QMapPrivate<QCString, QString>::find (this=0xcccccccd, k=@0xbf9faf94)
    at /usr/share/qt3/include/qmap.h:498
#6  0xb7ef51f9 in KCal::CustomProperties::nonKDECustomProperty (
    this=0x8187e1c, name=@0xbf9faf94) at /usr/share/qt3/include/qmap.h:698
#7  0xb7ef52fb in KCal::CustomProperties::customProperty (this=0x8187e1c, 
    app=@0xbf9fbac0, key=@0xbf9fbab8)
    at /tmp/buildd/kdepim-3.5.6.dfsg.1/./libkcal/customproperties.cpp:77
#8  0x0807709f in ?? ()
#9  0xbf9fbb50 in ?? ()
#10 0x08187e1c in ?? ()
#11 0xbf9fbac0 in ?? ()
#12 0xbf9fbab8 in ?? ()
#13 0xfffffff6 in ?? ()
#14 0x00000010 in ?? ()
#15 0x00000010 in ?? ()
#16 0x00000000 in ?? ()

Would you like to receive any other data?
Comment 3 Tommi Tervo 2007-06-27 15:22:49 UTC
*** Bug 147025 has been marked as a duplicate of this bug. ***
Comment 4 Thomas McGuire 2007-06-28 23:00:38 UTC
*** Bug 147023 has been marked as a duplicate of this bug. ***
Comment 5 Thomas McGuire 2007-06-28 23:00:48 UTC
*** Bug 147085 has been marked as a duplicate of this bug. ***
Comment 6 Thomas McGuire 2007-06-28 23:00:57 UTC
*** Bug 147337 has been marked as a duplicate of this bug. ***
Comment 7 Thomas McGuire 2007-07-14 16:39:52 UTC
*** Bug 146840 has been marked as a duplicate of this bug. ***
Comment 8 Michael Brade 2007-07-22 12:47:52 UTC
Since #147359 seems to have been fixed, is this bug a duplicate and now also fixed? Maybe it was a bug in Qt? I have never experienced this crash, so I cannot debug it...
Comment 9 Guillermo Antonio Amaral Bastidas 2007-10-13 22:39:07 UTC
COMATOSE BUG : Cannot reproduce

  If anybody reproduces this bug please contact me directly.

On to KDE4 :-)
Comment 10 Christophe Marin 2009-06-04 21:07:52 UTC
*** Bug 195247 has been marked as a duplicate of this bug. ***