I don't know totally for sure there, that's what happened with my
Slackware '96 (Kernel 2.0.28, I think?) distribution. And that was before
my driving motivation came a month ago to *really* learn UNIX/Linux and
use it. All that I can say is that I've never had a core dump since I've
installed Slackware 3.5.0 (kernel 2.0.34).
BTW, from whomever may know this answer, if we find an answer to a hard to
find question for Linux, where/how can we submit this so that the fix
becomes more known? Mostly, I'm talking about Slackware interacting with
Microsoft mice (X Windows doesn't seem to work without changing the
commandline of gpm in the startup scripts, and then using /dev/gpmdata as
the port... and it took me two weeks to find this answer)..... Where/how
to submit the info, though?
- Mike Trausch
On Thu, 3 Dec 1998, Alvaro M. Piffaretti wrote:
> 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.
> 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'.
> 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 ?
>
> best regards,
> Alvaro
>
