| Summary: | regression: konqueror crashes without backtrace on some sites, e.g. when loggin into mailman | ||
|---|---|---|---|
| Product: | [Applications] konqueror | Reporter: | S. Burmeister <sven.burmeister> |
| Component: | general | Assignee: | Konqueror Developers <konq-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | maksim |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
S. Burmeister
2005-11-15 11:47:06 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? can you provide me with the commands to use within gdb please? I am not familiar with the app. 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 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?) 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... |