Very Computer

I get occasional SIGSEGV, and solid SIGSEGV when I run a recent version
of kmail, and knode.
SUSE 7.0 w/ KDE2.1

Questions:
        1-Where is the kde core dump if anywhere?
        2-Any suggestions?
Thanks.
        Ag

You should get core dumps if you start the program with the
"--nocrashhandler" option. But you can also use the crash dialog to
generate a backtrace.

Quote:> 2-Any suggestions?

Not without a backtrace.

Greetings
Christian
--

At a first try you should upgrade to kde2.1.1. Rpms are available for Suse.

Quote:> Questions:
> 1-Where is the kde core dump if anywhere?

Normally there is no core dump. In case of a crash dr. konqi asks you what
to do.

Quote:> 2-Any suggestions?

You can use drkonqi to get a backtrace and make a bug report. Or, if you're
a programmer, you can use a de* and attach to the program when drkonqi
appears. Or force the de* to create a core file.

Mathias

I did found what happened:
    when I installed KDE 2.1.1 I just did not install the rpm file
"kdesupport-2.1.1-16.rpm"
So obviously some library files were missing, and used by few apps,
including kmail! (Not the old one).
For the developpers, I have seen this kind of problems before, when the
exception processing is bypassed, i.e you just open a (lib) file, assume
it always be there, and do not issue any message, when it fails.
It would be nice to have a wrapper for file opening to always issue an
error message before crashing when a file is missing. Exception
processing is rarely used, but saves seriuos headaches.
Same when a file permission is not appropriate: printing the file
path/name is a very good pointer to a fix.
Hope this may help someone.
Andre

I did found what happened:
    when I installed KDE 2.1.1 I just did not install the rpm file
"kdesupport-2.1.1-16.rpm"
So obviously some library files were missing, and used by few apps,
including kmail! (Not the old one).
For the developpers, I have seen this kind of problems before, when the
exception processing is bypassed, i.e you just open a (lib) file, assume
it always be there, and do not issue any message, when it fails.
It would be nice to have a wrapper for file opening to always issue an
error message before crashing when a file is missing.
Exception processing is rarely used, but can saves serious headaches.
Same when a file permission is not appropriate: printing the file
path/name is a very good pointer to a fix.
Hope this may help someone.
Andre

If a library file is missing the dynamic linker will complain and
the program will not start. I think that you had an old version of
the mimelib installed, which was compiled with a different compiler
or different compiler settings.
Unfortunally it is not possible to issue a warning in this case.

Greetings
Christian
--