This actually turned out to be a red herring. One of the
things I had to trace was an attempted read from /dev/ttyd0 in
which I was trying to go past the actual read. This appears to
be what thoroughly confused the trace.
There was a logic error in the signal handler which
caused
At 07:46 AM 3/6/2008, Martin McCormick wrote:
This actually turned out to be a red herring. One of the
things I had to trace was an attempted read from /dev/ttyd0 in
which I was trying to go past the actual read. This appears to
be what thoroughly confused the trace.
There was a
A SIGHUP signal to a running process needs a signal
handler like
signal( SIGHUP ,startlogging);
What sort of end statement needs to be in the function
called to allow program execution to resume back in the main
caller?
I had put a return; statement in the function and
At 03:26 PM 3/5/2008, Martin McCormick wrote:
A SIGHUP signal to a running process needs a signal
handler like
signal( SIGHUP ,startlogging);
What sort of end statement needs to be in the function
called to allow program execution to resume back in the main
caller?
I