Summary: | crashes with large output from command - not history related | ||
---|---|---|---|
Product: | [Applications] konsole | Reporter: | Kurt Hindenburg <khindenburg> |
Component: | general | Assignee: | Konsole Developer <konsole-devel> |
Status: | RESOLVED REMIND | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
Crash log from user
valgrind output from user |
Description
Kurt Hindenburg
2006-01-01 01:18:17 UTC
I can't reproduce this on my Gentoo system. I've left my 'ls -Rav /' going for almost an hour... no crashes... Kurt, The mentioned backtraces haven't been attached to this bug report. Do you still have them? Dave Jarvis <dave@joot.com> $ gdb /usr/local/src/kdebase-3.4.2/konsole/konsole/.libs/konsole This GDB was configured as "i586-suse-linux"...Using host libthread_db library "/lib/tls/libthread_db.so.1". (gdb) run Starting program: /usr/local/src/kdebase-3.4.2/konsole/konsole/.libs/konsole [Thread debugging using libthread_db enabled] [New Thread 1096624704 (LWP 11274)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1096624704 (LWP 11274)] 0x8e40f536 in ?? () (gdb) where #0 0x8e40f536 in ?? () #1 0x40c2d627 in QEventLoop::activateTimers () from /usr/lib/qt3/lib/libqt-mt.so.3 #2 0x40be6e2f in QEventLoop::processEvents () from /usr/lib/qt3/lib/libqt-mt.so.3 #3 0x40c4f8e9 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3 #4 0x40c4f7e6 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #5 0x40c3833f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3 #6 0x40079d8c in kdemain () from /opt/kde3/lib/libkdeinit_konsole.so #7 0x080486f2 in main (argc=1, argv=0xbfa69844) at konsole.la.cpp:2 Created attachment 17251 [details]
Crash log from user
Created attachment 17252 [details]
valgrind output from user
Unfortunately it looks like the backtraces have been produced with binaries that have little or no debugging information. Does the reporter know whether this crash occurs when displaying one particular file in the "ls" operation? Any updates from the user? Closing for now as there is not enough information to properly debug and fix the problem. Please re-open if answers to previous queries are forthcoming. |