Bug 56158 - crash while using autocomplete in FTP site
Summary: crash while using autocomplete in FTP site
Status: RESOLVED DUPLICATE of bug 54515
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-03-19 21:10 UTC by hughjonesd
Modified: 2003-03-19 21:33 UTC (History)
0 users

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 hughjonesd 2003-03-19 21:10:05 UTC
Version:           3.1.0 (using KDE 3.1.0)
Installed from:    SuSE
Compiler:          gcc version 2.95.3 20010315 (SuSE)
OS:          Linux (i686) release 2.4.18-4GB

I returned to an ftp site I had just visited, and used the autocomplete in Konqueror's address bar to finish the address, whereupon Konq crashed: backtrace as follows.

(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)...[New Thread 1024 (LWP 3398)]
(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)...
0x40f03099 in wait4 () from /lib/libc.so.6
#0  0x40f03099 in wait4 () from /lib/libc.so.6
#1  0x40f7dbd8 in __DTOR_END__ () from /lib/libc.so.6
#2  0x40db6072 in waitpid () from /lib/libpthread.so.0
#3  0x4056c4bb in KCrash::defaultCrashHandler ()
   from /opt/kde3/lib/libkdecore.so.4
#4  0x40db3a74 in pthread_sighandler () from /lib/libpthread.so.0
#5  <signal handler called>
#6  0x40abcfa9 in QString::QString () from /usr/lib/libqt-mt.so.3
#7  0x4198d8ba in khtml::Loader::servePendingRequests ()
   from /opt/kde3/lib/libkhtml.so.4
#8  0x4199003c in khtml::Loader::qt_invoke () from /opt/kde3/lib/libkhtml.so.4
#9  0x408b6b74 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#10 0x40b11335 in QSignal::signal () from /usr/lib/libqt-mt.so.3
#11 0x408cbfdd in QSignal::activate () from /usr/lib/libqt-mt.so.3
#12 0x408d13e0 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3
#13 0x4086b8da in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#14 0x4086b6e7 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#15 0x4050ae6b in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#16 0x40845a75 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#17 0x4082828d in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#18 0x4087bc80 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#19 0x4087bbc7 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#20 0x4086ba56 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#21 0x412ba67e in main () from /opt/kde3/lib/konqueror.so
#22 0x0804cfe6 in strcpy ()
#23 0x0804ddda in strcpy ()
#24 0x0804e29d in strcpy ()
#25 0x0804f197 in strcpy ()
#26 0x40e789ed in __libc_start_main () from /lib/libc.so.6
Comment 1 Maksim Orlovich 2003-03-19 21:33:32 UTC
That's a duplicated of the fixed (in 3.1.1) #54515 
 

*** This bug has been marked as a duplicate of 54515 ***