M.chandrasekhar wrote:
> Hi,
> Any one has idea of how to handle signaling in program run time errors.
> I mean not just signal handler..i want to know the exact reason of error.
> Well "extern int errno" is not updated when an abrupt signal is thrown like
> SIGSEGV etc..example. like we use gdb and find out with registers where
> error of memory occured can't we handle that in program itself..
>
> We can register signal handler but its (void (*)(int)) where we can only
> obtain signal number and my question is how to trap the exact error of that
> signal..
>
> -Regards
> chandra
>
>
man siginfo and sigaction

-- ced

--
Chuck Dillon
Senior Software Engineer
NimbleGen Systems Inc.