Bug 56944 - Konqueror crashed using the link "eBanking" on www.sparkasse-nuernberg.de
Summary: Konqueror crashed using the link "eBanking" on www.sparkasse-nuernberg.de
Status: RESOLVED DUPLICATE of bug 54515
Alias: None
Product: konqueror
Classification: Applications
Component: khtml (show other bugs)
Version: 3.1
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-04-07 12:36 UTC by Andreas Meinl
Modified: 2003-05-12 18:32 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 Andreas Meinl 2003-04-07 12:36:20 UTC
Version:           3.1 (using KDE KDE 3.1)
Installed from:    SuSE RPMs
Compiler:          g++ (GCC) 3.2 
OS:          Linux

Konqueror crashed after I have clicked on the link "eBaning" on the website http://www.sparkasse-nuernberg.de/ and "The KDE Crash Handler" appeared with following bugtrace:

(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)...(no debugging symbols found)...
(no debugging symbols found)...[New Thread 1024 (LWP 3120)]
(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)...0x411d48c9 in wait4 () from /lib/libc.so.6
#0  0x411d48c9 in wait4 () from /lib/libc.so.6
#1  0x4124fc90 in __DTOR_END__ () from /lib/libc.so.6
#2  0x4102fa93 in waitpid () from /lib/libpthread.so.0
#3  0x40743b0d in KCrash::defaultCrashHandler(int) ()
   from /opt/kde3/lib/libkdecore.so.4
#4  0x4102d12b in pthread_sighandler () from /lib/libpthread.so.0
#5  <signal handler called>
#6  0x00200020 in ?? ()
#7  0x41bfe128 in khtml::Loader::qt_invoke(int, QUObject*) ()
   from /opt/kde3/lib/libkhtml.so.4
#8  0x40ac2309 in QObject::activate_signal(QConnectionList*, QUObject*) ()
   from /usr/lib/libqt-mt.so.3
#9  0x40da1242 in QSignal::signal(QVariant const&) ()
   from /usr/lib/libqt-mt.so.3
#10 0x40adc5c8 in QSignal::activate() () from /usr/lib/libqt-mt.so.3
#11 0x40ae3613 in QSingleShotTimer::event(QEvent*) ()
   from /usr/lib/libqt-mt.so.3
#12 0x40a642e4 in QApplication::internalNotify(QObject*, QEvent*) ()
   from /usr/lib/libqt-mt.so.3
#13 0x40a63e4b in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/libqt-mt.so.3
#14 0x406d5fc9 in KApplication::notify(QObject*, QEvent*) ()
   from /opt/kde3/lib/libkdecore.so.4
#15 0x40a3d233 in QEventLoop::activateTimers() () from /usr/lib/libqt-mt.so.3
#16 0x40a1abe4 in QEventLoop::processEvents(unsigned) ()
   from /usr/lib/libqt-mt.so.3
#17 0x40a77fa6 in QEventLoop::enterLoop() () from /usr/lib/libqt-mt.so.3
#18 0x40a77e48 in QEventLoop::exec() () from /usr/lib/libqt-mt.so.3
#19 0x40a64511 in QApplication::exec() () from /usr/lib/libqt-mt.so.3
#20 0x400533f7 in main () from /opt/kde3/lib/konqueror.so
#21 0x4114f4a2 in __libc_start_main () from /lib/libc.so.6
Comment 1 Thiago Macieira 2003-04-07 15:01:59 UTC
Cannot reproduce HEAD 20030405. The site loads fine and apparently even 
rendered ok. 
Comment 2 Maksim Orlovich 2003-05-12 18:32:15 UTC
Looks like a duplicate of #54515 to me; that was fixed by Dirk in 3.1.1.  
  
 

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