Sig handler causing core dump

[Mark Brackett]

I'm a newbie to C programming...so go easy. ;)
I'm forking child processes, and registering a signal handler with the following:
signal(SIGTERM, DieServer);
signal(SIGINT, DieServer);

DieServer is the following:
volatile sig_atomic_t dying_in_progress = 0;
void DieServer(int sig){
int result;
char dummy[0];
if(dying_in_progress) raise(sig);
dying_in_progress = 1;

// Now do the clean up actions:
if(debug==1) printf("SERVER PARENT->Received SIGEVENT %d.\n",sig);
wait();
close(client_sockfd);
read(server_sockfd,dummy,0);
result = close(server_sockfd);
if(result==-1){
if(debug==1) printf("SERVER PARENT->Could not close socket\n");
perror("WARNING");
}
signal(sig, SIG_DFL);
raise(sig);
}

The wait() causes a core dump if there's no children. How do I fix this?

[Artie Gold]

Mark Brackett wrote:

I'm a newbie to C programming...so go easy. ;)
OK. I'll be gentle.
I'm forking child processes, and registering a signal handler with the following:
Whoops. There is no such thing as `forking' in standard C...
signal(SIGTERM, DieServer);
signal(SIGINT, DieServer);

DieServer is the following:
volatile sig_atomic_t dying_in_progress = 0;
void DieServer(int sig){
int result;
char dummy[0];
if(dying_in_progress) raise(sig);
dying_in_progress = 1;

// Now do the clean up actions:
if(debug==1) printf("SERVER PARENT->Received SIGEVENT %d.\n",sig);
wait();
close(client_sockfd);
read(server_sockfd,dummy,0);
result = close(server_sockfd);
if(result==-1){
if(debug==1) printf("SERVER PARENT->Could not close socket\n");
perror("WARNING");
}
signal(sig, SIG_DFL);
raise(sig);
}

The wait() causes a core dump if there's no children. How do I fix this?

....nor read(), nor close() nor wait().

There *are* such things in POSIX, hence posting your question to
news:comp.unix.programmer would be the best course of action.

Gentle enough for you? ;-)

See you over there.

HTH,
--ag

--
Artie Gold -- Austin, Texas

http://it-matters.blogspot.com

[Dave Vandervies]

In article <de**************************@posting.google.com >,
Mark Brackett <br******@ufl.edu> wrote:

I'm a newbie to C programming...so go easy. ;)
I'm forking child processes, <snip>The wait() causes a core dump if there's no children. How do I fix this?

forking child processes, wait(), and a lot of what was in between that I
snipped are beyond the scope of the C language and therefore inappropriate
for comp.lang.c.

I suspect that comp.unix.programmer would be a better place to ask this.
dave

--
Dave Vandervies dj******@csclub.uwaterloo.ca
Hmm, a quote for posterity: "calling strlen() is a lengthy operation."
Is calling memmove() a 'moving experience?'
--Mike Wahler in comp.lang.c

[Mark Brackett]

dj******@csclub.uwaterloo.ca (Dave Vandervies) wrote in message news:<cm**********@rumours.uwaterloo.ca>...

In article <de**************************@posting.google.com >,
Mark Brackett <br******@ufl.edu> wrote:

I'm a newbie to C programming...so go easy. ;)
I'm forking child processes,

<snip>

The wait() causes a core dump if there's no children. How do I fix this?

forking child processes, wait(), and a lot of what was in between that I
snipped are beyond the scope of the C language and therefore inappropriate
for comp.lang.c.

I suspect that comp.unix.programmer would be a better place to ask this.
dave

Doh! Sorry for the faux pas....I'll try again over there. Thanks for
the gently delivered heads-ups.

--Mark Brackett