Well ... where to begin is by considering this part of the gdb output:
>Core was generated by `kaudioserver'.
>Program terminated with signal 11, Segmentation fault.
kaudioserver (whatever that is - I assume some piece of KDE) is segfaulting.
The usual cause of a segfault is an attempt by a program to access a
location in memory that has not been allocated to it by the kernel.
If this attempt is accidental (not a botched virus, for example), it can
occur because a line tries to read to or write from a location "in" an array
that is past the end of the array. (That is, you have an array of, say,
integers myints[], indexed from myints[0] to myints[19], and you try to
write to myints[20].) Just about anyone who write programs for Unix/Linux
systems has seen this kind of segfault, simply because it is such an easy
programming error to make. It can also occur if the program tries to access
a dymanically-allocated variable after its memory has been released by the
program ... another common programming error. (Alas, I speak form experience
in both instances.)
So ... where to begin is with kaudioserver. Personally, I'd first see if RH
has an updated version of the program that you can switch to -- if it is a
common problem, not one caused by some oddity of your setup, the creator
will surely have fixed it in the 8 or so months since RH 6.0 was released.
If not -- or if you try this and still get segfaults -- you need to see if
the program has to be run as root, or with setuid enabled, to run
successfully. DON'T do this solution if the docs don't say you should --
doing it may eliminate the segfaults (since root-run programs have more
privileges than user-run ones) but not the problem that is causing the
segfaults.
If not, then try running the program under strace and seeing where the
segfault occurs. Since I know nothing about what kaudioserver does (save the
little I can guess from its name) and nothing about the system hardware it
is interacting with, I can't be more specific.
Finally, you might consider an update of your overall system to RH 6.1,
kernel 2.2.13 or 2.2.14 (not sure which is the latest RH supplies). RH 6.0
came out while the 2.2.x kernel didn't really deserve to be called stable,
and generally I recall seeing a lot of bug reports about apps in it as well.
BTW, why did you conclude with:
>Please respond to me personally (i.e. [EMAIL PROTECTED])
I hope it was just because you wanted to see responses faster than you would
if you waited for the list to forward them. It is considered by many
(including me) to be ill-mannered to ask for help from a list that you do
not subscribe to.
At 03:18 PM 2/5/00 -0200, Richard Spencer wrote:
>Can anyone point me in the right direction? I seem to get a core dump everyday,
>and today I looked into it:
[details deleted]
>I'm running KDE 1.1, RH 6.0, kernel 2.2.5, and I wonder where to begin in order
>to put an end to these core dumps!
>
>Please respond to me personally (i.e. [EMAIL PROTECTED])
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
Palo Alto, CA [EMAIL PROTECTED]
----------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
