Summary: | Konsole crashes after some output. If started again, might crash even faster. | ||
---|---|---|---|
Product: | [Applications] konsole | Reporter: | Arto Viitanen <arto.viitanen> |
Component: | general | Assignee: | Konsole Developer <konsole-devel> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | 1.6.4 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Arto Viitanen
2006-07-31 19:04:57 UTC
The interesting part is this: ==5691== 230 errors in context 6 of 6: ==5691== Invalid read of size 2 ==5691== at 0x50CA680: QLatin15Codec::toUnicode(char const*, int) const (in /usr/lib/qt3/lib/libqt-mt.so.3.3.6) ==5691== by 0x50C8529: QTextStatelessDecoder::toUnicode(char const*, int) (in /usr/lib/qt3/lib/libqt-mt.so.3.3.6) ==5691== by 0x409A653: TEmulation::onRcvBlock(char const*, int) (TEmulation.cpp:332) ==5691== by 0x40A11B8: TESession::onRcvBlock(char const*, int) (session.cpp:746) ==5691== by 0x40AB6F9: TESession::qt_invoke(int, QUObject*) (session.moc:462) ==5691== by 0x4DCFD3C: QObject::activate_signal(QConnectionList*, QUObject*) (in /usr/lib/qt3/lib/libqt-mt.so.3.3.6) ==5691== by 0x4085F37: TEPty::block_in(char const*, int) (TEPty.moc:143) ==5691== by 0x408606A: TEPty::dataReceived(KProcess*, char*, int) (TEPty.cpp:233) ==5691== by 0x408DF32: TEPty::qt_invoke(int, QUObject*) (TEPty.moc:164) ==5691== by 0x4DCFD3C: QObject::activate_signal(QConnectionList*, QUObject*) (in /usr/lib/qt3/lib/libqt-mt.so.3.3.6) ==5691== by 0x49CEEED: KProcess::receivedStdout(KProcess*, char*, int) (kprocess.moc:152) ==5691== by 0x49CEFC7: KProcess::childOutput(int) (kprocess.cpp:853) ==5691== Address 0x6899924 is 0 bytes after a block of size 4 alloc'd ==5691== at 0x40217E9: operator new[](unsigned) (in /usr/lib/valgrind/x86-linux/vgpreload_memcheck.so) ==5691== by 0x509FFEC: (within /usr/lib/qt3/lib/libqt-mt.so.3.3.6) ==5691== by 0x50A12B1: QString::fromLatin1(char const*, int) (in /usr/lib/qt3/lib/libqt-mt.so.3.3.6) ==5691== by 0x50CA66A: QLatin15Codec::toUnicode(char const*, int) const (in /usr/lib/qt3/lib/libqt-mt.so.3.3.6) ==5691== by 0x50C8529: QTextStatelessDecoder::toUnicode(char const*, int) (in /usr/lib/qt3/lib/libqt-mt.so.3.3.6) ==5691== by 0x409A653: TEmulation::onRcvBlock(char const*, int) (TEmulation.cpp:332) ==5691== by 0x40A11B8: TESession::onRcvBlock(char const*, int) (session.cpp:746) ==5691== by 0x40AB6F9: TESession::qt_invoke(int, QUObject*) (session.moc:462) ==5691== by 0x4DCFD3C: QObject::activate_signal(QConnectionList*, QUObject*) (in /usr/lib/qt3/lib/libqt-mt.so.3.3.6) ==5691== by 0x4085F37: TEPty::block_in(char const*, int) (TEPty.moc:143) ==5691== by 0x408606A: TEPty::dataReceived(KProcess*, char*, int) (TEPty.cpp:233) ==5691== by 0x408DF32: TEPty::qt_invoke(int, QUObject*) (TEPty.moc:164) this looks a bit like a Qt bug actually, but as I can't reproduce this with my home dir I'm lost It has something to do with the international settings. Being from Finland, I use LC_ALL="fi_FI@euro" settings. If I set it to LC_ALL="c", no crashing happends. But when I set it back to "fi_FI@euro", konsole crashes after some "ls" commands. It might be, that I have some files that have scandinavian letters on their names, but I remember konsole crashing on other programs also, where I think no Latin-9 letters were shown. Hello Arto, Does it matter which directories you run 'ls' on (when LC_ALL is set to "fi_FI@euro" )? - particularly I am interested in the result when running ls on a directory which definitely does have files with Scandinavian letters in their names versus a directory which has only files with plain ASCII letters in their names. Robert Knight wrote: [bugs.kde.org quoted mail] I have not seen the problem for some time (I have now OpenSUSE 10.2), so I assumed the problem went away on some newer KDE. When I had the problem, it did not matter (I try not to use Scandinavian letters on my filenames since programs have problems with names that do not use USASCII letters) what letters the file had. After some pages of ls listing, the konsole crashed. -- Arto Viitanen I think I have seen this reported elsewhere, it would seem to be a Qt issue. |