According to Alvaro M. Piffaretti: While burning my CPU.
>
> Hi all,
>
> Everything I have read about states that core dumps files should be
> core.prgfile where prgfile, after the dot would be the program that
> caused the segmentation fault.
No the file is called just "core".
> Well, I have two slackware installations (3.1 and 3.4) and kernels
> 2.0.30 and 2.0.34, but in both of them when I get a core dump
> the filename is just 'core'.
To see which process or progam is causeing the core dump, use gdb;
'gdb -c core' in the directory where the file is situated.
You can find out a lot more about what caused the program to dump core with
different gdb commands, "man gdb" might help you.
> The same for faulty programs written in C.
> Now I am troubleshooting a core dump that I guess is from a KDE
> component, and that feature could help me.
> Does anyone know if there is an env. var or something like that
> that could be responsible for that ?
It could possably be a configuration fault on your system, or something like
an "overclocked CPU" bad memory.. No swap partition.....
There are so many causes...
>
> best regards,
> Alvaro
>
--
Regards Richard.
[EMAIL PROTECTED]
