Summary: | kile crashes when inserting ' when automatic brackets are used | ||
---|---|---|---|
Product: | [Applications] kile | Reporter: | Christian Trippe <christiandehne> |
Component: | general | Assignee: | Michel Ludwig <michel.ludwig> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | 2.0.84 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | kilerc which triggers the bug |
Description
Christian Trippe
2010-02-03 10:57:42 UTC
I'm sorry but I have been unable to reproduce this issue with the latest SVN version of kdelibs and Kile. Can you maybe install some debug packages so that we could get a more meaningful backtrace? Thanks for your response. (In reply to comment #1) > I'm sorry but I have been unable to reproduce this issue with the latest SVN > version of kdelibs and Kile. > I tried now with a new user and could not reproduce it either. However if I copy my kilerc to the new user I can reproduce it. I will attach my kilerc. I also noticed that it usually does not crash if I type ' in normal mode but it crashes nearly every time if I am in math mode . So please try something like $K_l' Sorry that I did not check these facts before. > Can you maybe install some debug packages so that we could get a more > meaningful backtrace? I was not really successful here. I hoped I had the most useful debug packages already installed as DrKonqi claimed that my backtrace was good. However I installed a few more. Now I get the following when runing kile in gdb when typing $K_l' (and waiting a bit hitting return) Qt has caught an exception thrown from an event handler. Throwing exceptions from an event handler is not supported in Qt. You must reimplement QApplication::notify() and catch all exceptions there. terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Program received signal SIGABRT, Aborted. 0xffffe430 in __kernel_vsyscall () (gdb) bt #0 0xffffe430 in __kernel_vsyscall () #1 0xb5ed90cf in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #2 0xb5eda9e7 in abort () at abort.c:88 #3 0xb60ed03f in __gnu_cxx::__verbose_terminate_handler () at ../../../../libstdc++-v3/libsupc++/vterminate.cc:93 #4 0xb60ead53 in __cxxabiv1::__terminate (handler=0xb60ecef0 <__gnu_cxx::__verbose_terminate_handler()>) at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:38 #5 0xb60ead8f in std::terminate () at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:48 #6 0xb60eae2a in __cxxabiv1::__cxa_rethrow () at ../../../../libstdc++-v3/libsupc++/eh_throw.cc:116 #7 0xb6dbfbd0 in QEventLoop::exec (this=0xbfffe9d4, flags=...) at kernel/qeventloop.cpp:214 #8 0xb6dc3bf0 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981 #9 0xb6257354 in QApplication::exec () at kernel/qapplication.cpp:3577 #10 0x0820d493 in main (argc=1, argv=0xbffff0a4) at /usr/src/debug/kile-trunk-r1055245/src/main.cpp:167 Created attachment 40585 [details]
kilerc which triggers the bug
Another thing, did you have automatic spell checking activated when inserting the quotes? If so, then this could be bug 225867. (In reply to comment #4) > Another thing, did you have automatic spell checking activated when inserting > the quotes? Yes, I have it enabled. Without automatic spell checking I am unable to reproduce the crash. Ok, this is bug 225867 then. Thanks. *** This bug has been marked as a duplicate of bug 225867 *** |