Member Discussions

Can someone recommend a free site where I can post a problem I am having with my shell? I have not found the answer through Google and reading some old college books and contacting my host hasn't worked so far (they are responding, just have recommended things I have already tried).

Nope. What's the problem?

-Crat
http://lpmuds.net

I'm am trying to set my shell (csh) to create a core file when my mud crashes. Even creating this simple program and running it doesn't seem to create a core file:

#include<stdio.h>
#include<stdlib.h>


int main(void)
{
char *foo = NULL;

foo[3] = 'c';
printf("done");
}

if I type "gcc -g crash.c -o test" and then type "test", no output is shown and no core is created. The only thing I have found is to make sure my corefilesize is set to unlimited, but it seems to me that it already is:

[scourge@indecent ~]$ limit
cputime unlimited
filesize unlimited
datasize unlimited
stacksize 10240 kbytes
coredumpsize unlimited
memoryuse 30000 kbytes
vmemoryuse unlimited
descriptors 1024
memorylocked 30000 kbytes
maxproc 7168

Try typing "./test" instead of "test". I _think_ "test" itself is an internal command in csh*.

[*] At least I know it is in bash.

hmm... well I renamed it to thiswillcrash and needed the ./
I could have sworn I tried different names before and didn't get a core, but this time I did. So it seems my shell is set correctly...

So now the question is why doesn't my mud create one? The core can't possibly be more than 77MB (HD space I have left), can it?

On another note, why do I need the ./? I thought as long as it was set as an executable you just had to type the filename?

./filename indicates that it should attempt to execute a file in the current directory (".") as opposed to one in a directory listed by the $PATH environment variable. $PATH generally includes global programs installed by your operating system for all users, but by default does not include the working directory.

You could try adding this to your startup file:

# Set limits.
limit coredumpsize unlimited
limit stack 1024k

http://www.linuxquestions.org/

Hmm, sometimes the "*" does matter. Are we indeed talking Linux here, or one of the commercial UNIXes? For example, Sun Solaris has coreadm that can configure global core dump policies, like disabling them, or having them saved in a single directory.

Hmm, sometimes the "*" does matter

Red Hat.

I did more experimenting and found that the mud did create a core when I ran it without the startup script. My host gave me 4 lines to add to the startup script and now it is working.

Thanks to all that replied :)