[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 197739] SemNotes (semnapp) crashed and caused the signal 11
From:       Andreas Pakulat <apaku () gmx ! de>
Date:       2009-06-25 6:45:21
Message-ID: 20090625064522.37B6B172AC () immanuel ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=197739


Andreas Pakulat <apaku@gmx.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |UPSTREAM
         AssignedTo|kdevelop-bugs@kdevelop.org  |kdelibs-bugs@kde.org




--- Comment #4 from Andreas Pakulat <apaku gmx de>  2009-06-25 08:45:05 ---
(In reply to comment #3)
> To Andreas Pakulat:
> ===================
> Correct, but the last KDE procedure call on the stack was 
> 
> #17 0x034833cf in KTextEdit::keyPressEvent (this=0x959a0d0, event=0xbfa2095c)
> at /usr/src/debug/kdelibs-4.2.4/kdeui/widgets/ktextedit.cpp:998
> 
> so I reckon it can happen to any KDE4libs api user

No, it can happen to anybody using Qt, just because there's a KDE class in the
stacktrace doesn't automatically mean it happens only with KDE. In particular
if you look at the relevant code in KTextEdit::keyPressEvent() you'll notice
that all it does is forward the event to the QTextEdit class. So the event just
passes through the KDE class and is then again in Qt code and thats where it
crashes. So as I said, report to the right people, KDE cannot do anything about
this.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

_______________________________________________
KDevelop-bugs mailing list
KDevelop-bugs@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-bugs
[prev in list] [next in list] [prev in thread] [next in thread]