Short description

The application Konqueror (konqueror) crashed and caused the signal 11
(SIGSEGV).

What is this ?

An application mostly receives the SIGSEGV signal due to a bug in the
application. The application was asked to save it's documents.

What can I do ?

You might want to send a bug report to the author. Please include as much
information as possible, maybe the original documents. If you have a way to
reproduce the error, include this also.



I don't know why I would get this, when I have only installed Samba 2.2.8a
and nothing else. The only other thing that I have done is run the 'SETUP'
for 'Apsfilter', and that comes with Slack 9.0 .

The only other nonstock software on the computer is the NVIDIA driver,
which never caused any problems before.
Not to mention that I get this error even without the NVIDIA driver, by
using the generic 'nv' driver included with Slack.

Other than the video driver, and Samba, I have only used stuff that was
included with Slack 9, such as Apsfilter.

All that I have to do is close a Conqueror window to get this error to pop
up.

Here is the 'Backtrace' output :

(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 16384 (LWP 420)]

0x410d0f29 in wait4 () from /lib/libc.so.6
#0 0x410d0f29 in wait4 () from /lib/libc.so.6
#1 0x41151234 in __DTOR_END__ () from /lib/libc.so.6
#2 0x40ee6103 in waitpid () from /lib/libpthread.so.0
#3 0x40633c4d in KCrash::defaultCrashHandler(int) ()
from /opt/kde/lib/libkdecore.so.4
#4 <signal handler called>
#5 0x40c17fc7 in QGDict::unlink_ascii(char const*, void*) ()
from /usr/lib/qt/lib/libqt-mt.so.3
#6 0x40c18474 in QGDict::take_ascii(char const*) ()
from /usr/lib/qt/lib/libqt-mt.so.3
#7 0x403e1dc1 in KActionCollection::_take(KAction*) ()
from /opt/kde/lib/libkdeui.so.4
#8 0x403e1f26 in KActionCollection::take(KAction*) ()
from /opt/kde/lib/libkdeui.so.4
#9 0x403d1790 in KAction::~KAction() () from /opt/kde/lib/libkdeui.so.4
#10 0x409adbf2 in QObject::~QObject() () from /usr/lib/qt/lib/libqt-mt.so.3
#11 0x403e1707 in KActionCollection::~KActionCollection() ()
from /opt/kde/lib/libkdeui.so.4
#12 0x409df508 in QWidget::~QWidget() () from /usr/lib/qt/lib/libqt-mt.so.3
#13 0x40a8a6ef in QMainWindow::~QMainWindow() ()
from /usr/lib/qt/lib/libqt-mt.so.3
#14 0x404330ae in KMainWindow::~KMainWindow() ()
from /opt/kde/lib/libkdeui.so.4
#15 0x4003c388 in KParts::MainWindow::~MainWindow() ()
from /opt/kde/lib/libkparts.so.2
#16 0x418f4781 in KonqMainWindow::~KonqMainWindow() ()
from /opt/kde/lib/konqueror.so
#17 0x409ae623 in QObject::event(QEvent*) () from /usr/lib/qt/lib/libqt-mt.so.3
#18 0x409e4c4c in QWidget::event(QEvent*) () from /usr/lib/qt/lib/libqt-mt.so.3
#19 0x40a8c3a2 in QMainWindow::event(QEvent*) ()
from /usr/lib/qt/lib/libqt-mt.so.3
#20 0x409528c4 in QApplication::internalNotify(QObject*, QEvent*) ()
from /usr/lib/qt/lib/libqt-mt.so.3
#21 0x4095208b in QApplication::notify(QObject*, QEvent*) ()
from /usr/lib/qt/lib/libqt-mt.so.3
#22 0x405b8c69 in KApplication::notify(QObject*, QEvent*) ()
from /opt/kde/lib/libkdecore.so.4
#23 0x40953658 in QApplication::sendPostedEvents(QObject*, int) ()
from /usr/lib/qt/lib/libqt-mt.so.3
#24 0x40966749 in QEventLoop::enterLoop() () from /usr/lib/qt/lib/libqt-mt.so.3
#25 0x40966608 in QEventLoop::exec() () from /usr/lib/qt/lib/libqt-mt.so.3
#26 0x40952af1 in QApplication::exec() () from /usr/lib/qt/lib/libqt-mt.so.3
#27 0x418ef457 in main () from /opt/kde/lib/konqueror.so
#28 0x0804cb41 in strcpy ()
#29 0x0804d7fb in strcpy ()
#30 0x0804dd04 in strcpy ()
#31 0x0804e9b9 in strcpy ()
#32 0x41038bb4 in __libc_start_main () from /lib/libc.so.6

Does anyone have an idea of what is causing this ?

JC

I believe that the signal 11 is a buffer overflow ie: the program tried to assign some data to a memory location that doesn't exist or is too small.

In any event, it is difficult to fix this sort of thing unless you speak C++ as a second language. If it is too much of a nuisance to live with then you may have to upgrade to a newer version of konq...no easy task in itself, as it is deeply integrated with kde.

Thanks for the reply. Actually, I do speak C++, and ASM. The only problem is that all of my experience is in Win32. As far as a debugger, I use SoftIce, and For a C++ compiler I use MSVC++.

I'm in a different element in Linux. Since I started in Slackware (1 1/2 months ago), I have spent all of my time getting my hardware to work properly, and setting up Samba for a file and print server with Windows clients. So I have spent very little time just looking at code, and trying to figure anything out.

Maybe this is the reason that I will dive into some code.
bulliver, would you happen to know anything that might help me in this matter ?

edit : BTW, do you know what typically causes these buffer errors ? And how would I set up an enviroment to debug with ?
If I am thinking in terms of debugging in Windows, I would set breakpoints in Softice, and then backtrace from wherever the breakpoint call is made.
How would I set something like this up in Linux?
JC

i've used many versions of kde, and i would often get
that error on more than half of the versions.
mostly between 1.3 and 2.0 tho

you could without too much trouble install a newer
or older version of kde. I've compiled my own several
times. version 2.2.2 might be the most stable, or
do i mean 2.2.

Sorry, I'm just trying to get my head around python right now. C++ is out of my grasp. I hope to teach it to myself after I'm more comfortable with python and OO programming in general.

I can tell you that if you really want to inspect and debug the code there are a number of tools to do this.

Kdevelop is an ide for kde/C++ with a built in debugger.
There is also the Gnu debugger (gdb???) but I have no clue how to use it. You probably have both installed already....

A few queries in the programming forum of this site should get you on the right track.

JC

Follow up :

Since I was feeling lazy, I decided to ditch the debugging approach, and just reinstalled Slack 9.0 . I know that it was the whimpy way out, but I did save time, and I discovered something.

This was definitely a software problem, because the problem has disappeared with the new install. I have set up the system just as before ( but with no additional packages installed) and I do not see the errors anymore.

This tells me that I screwed something up before, and just didn't catch it.
At least I don't have to worry about any of my hardware being to blame (takes a sigh of relief).

Hopefully this will help someone who finds the same error on their system. It's worth a shot to re-install. It couldn't hurt. I equate this incident as being synonymous with doing something in Windows to screw up explorer. It's always agravating to install something on a Windows box, and then your computer pops up all those wonderfull illegal operation or page fault errors in explorer.

These are my conclusions, and they could be wrong. I'm only thinking like a guy that has dealt with Windows for 10 years.

JC

one thing to try before that would be deleting
the .kde directory in your home dir. that would make kde
set up as if it had never been run. it could have just
been a messed up config file.

Thanks for the info whansard . That's cool to know. I could have possibly saved myself a reinstall had I known to try that first.

JC

that goes for other linux software too.
figuring out the name of the config file, usually the
name of the app if it's not kde or gnome, and deleting
it from your home dir. that's helped me out many times.