[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    Bug#23350: crash on www.tech-report.com
From:       Louis R Nagy <LRNagy () iname ! com>
Date:       2001-03-31 20:02:19
[Download RAW message or body]

On Saturday 31 March 2001 14:58, you wrote:
> On Fre, 30 Mär 2001, LRNagy@iname.com wrote:
> > (no debugging symbols found)...(no debugging symbols found)...
> > (no debugging symbols found)...(no debugging symbols found)...
> > (no debugging symbols found)...0x40e6d1d9 in wait4 () from /lib/libc.so.6
> > #0  0x40e6d1d9 in wait4 () from /lib/libc.so.6
> > #1  0x40edcf2c in __check_rhosts_file () from /lib/libc.so.6
> > #2  0x40620928 in KCrash::defaultCrashHandler () from
> > /usr/lib/libkdecore.so.3
> >
> > #3  0x40de1b68 in killpg () from /lib/libc.so.6
> > #4  0x40664790 in KLibrary::slotTimeout () from /usr/lib/libkdecore.so.3
> > #5  0x408c6bcb in QObject::activate_signal () from /usr/lib/libqt.so.2
> > #6  0x4091ee52 in QTimer::timeout () from /usr/lib/libqt.so.2
> > #7  0x408ff6cb in QTimer::event () from /usr/lib/libqt.so.2
> > #8  0x4086f761 in QApplication::notify () from /usr/lib/libqt.so.2
> > #9  0x405bb5f9 in KApplication::notify () from /usr/lib/libkdecore.so.3
> > #10 0x4083d9f6 in qt_activate_timers () from /usr/lib/libqt.so.2
> > #11 0x4083b704 in QApplication::processNextEvent () from
> > /usr/lib/libqt.so.2 #12 0x4087158c in QApplication::enter_loop () from
> > /usr/lib/libqt.so.2 #13 0x4083af27 in QApplication::exec () from
> > /usr/lib/libqt.so.2 #14 0x4003df60 in main () from /usr/lib/konqueror.so
> > #15 0x080498c8 in ?? ()
> > #16 0x08378248 in ?? ()
>
> this happens only with www-tech-report.com ? I don't think so. some of the
> parts loaded by konqueror seems to be crashing upon typing the url. can't
> be specific to this url, is it ?
>
>
> Dirk

Dirk,

I'm not 100% sure. At the time I visited this URL things crashed and so I 
sent this in.  I wasn't able to reproduce it.

I had a previous problem which turned out to be a buggy pluggin which caused 
things to crash when konq unloaded it and this may have been the cause of 
this problem since the stack trace is similar. In fact I thought this was 
closed as a result of that fix as well (23318).

I would close this one and say fixed with 23318 if you don't see anything 
unusual.

Thanks,
Lou

[prev in list] [next in list] [prev in thread] [next in thread]