Bug 116411 - regression: konqueror crashes without backtrace on some sites, e.g. when loggin into mailman
Summary: regression: konqueror crashes without backtrace on some sites, e.g. when logg...
Status: RESOLVED DUPLICATE of bug 116176
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: 2005-11-15 11:47 UTC by S. Burmeister
Modified: 2005-11-17 15:44 UTC (History)
1 user (show)

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 S. Burmeister 2005-11-15 11:47:06 UTC
Version:            (using KDE KDE 3.5.0)
Installed from:    SuSE RPMs
OS:                Linux

Since RC1 I get konqueror crashing without a backtrace (drkonqi).

E.g. after trying to log into mailman-admin:
https://mailmanserver/mailman/admin/mailinglist

or
http://www.google.de/search?q=ascii+note+letter&ie=UTF-8&oe=UTF-8

I middle-click on:
ASCII - ISO 8859-1 Table with HTML Entity Names and
Special ASCII characters in HTML

the tabs get opened in the background and jonqueror crashes after some seconds.
Comment 1 Maksim Orlovich 2005-11-15 15:55:00 UTC
Hi.. I can not reproduce this based on your instructions.. Could you by any chance try running konqueror through gdb, and see if you get a backtrace in that?
Comment 2 S. Burmeister 2005-11-16 20:43:11 UTC
can you provide me with the commands to use within gdb please? I am not familiar with the app.
Comment 3 Maksim Orlovich 2005-11-16 22:10:19 UTC
1) open a terminal

2) type: 'gdb konqueror'
3) type: 'run'
4) do whatever causes it to crash
5) type: 'bt'

that should produce the backtrace
Comment 4 S. Burmeister 2005-11-16 22:49:05 UTC
I hope thsi helps:

[Thread debugging using libthread_db enabled]
[New Thread 1097166240 (LWP 4225)]
(no debugging symbols found)
kdecore (KAction): WARNING: KActionCollection::KActionCollection( QObject *paren                                                                                                   t, const char *name, KInstance *instance )
*** glibc detected *** corrupted double-linked list: 0x4020d8d8 ***

---Type <return> to continue, or q <return> to quit---
Program received signal SIGABRT, Aborted.
[Switching to Thread 1097166240 (LWP 4225)]
0xffffe410 in __kernel_vsyscall ()
(gdb) bt
#0  0xffffe410 in __kernel_vsyscall ()
#1  0x40118541 in raise () from /lib/tls/libc.so.6
#2  0x40119dbb in abort () from /lib/tls/libc.so.6
#3  0x4014e8b5 in __libc_message () from /lib/tls/libc.so.6
#4  0x40154842 in malloc_printerr () from /lib/tls/libc.so.6
#5  0x4015494f in malloc_consolidate () from /lib/tls/libc.so.6
#6  0x4020d8b4 in main_arena () from /lib/tls/libc.so.6
#7  0x4020d8c4 in main_arena () from /lib/tls/libc.so.6
#8  0x0887d1b8 in ?? ()
#9  0x4020d8d8 in main_arena () from /lib/tls/libc.so.6
#10 0x00000000 in ?? ()
#11 0x00000000 in ?? ()
#12 0x4020bff4 in ?? () from /lib/tls/libc.so.6
#13 0x4020d8a0 in mp_ () from /lib/tls/libc.so.6
#14 0x00000000 in ?? ()
#15 0xbff7115c in ?? ()
#16 0x40155534 in _int_malloc () from /lib/tls/libc.so.6
Previous frame inner to this frame (corrupt stack?)
Comment 5 Maksim Orlovich 2005-11-16 23:19:32 UTC
not especially, since it's missing information about KDE code, but it makes it two of you w/the same problem (one other reporter found exactly the same thing, using the same distro). Something really wrong is happening here...

Comment 6 Dirk Mueller 2005-11-17 15:44:47 UTC

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