Re: Why I could not catch the signals on HP_UX?
Ulrich.Teichert_at_gmx.de
Date: 06/28/05
- Previous message: Sandy: "Re: Why I could not catch the signals on HP_UX?"
- In reply to: Sandy: "Re: Why I could not catch the signals on HP_UX?"
- Next in thread: Sandy: "Re: Why I could not catch the signals on HP_UX?"
- Reply: Sandy: "Re: Why I could not catch the signals on HP_UX?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 28 Jun 2005 18:35:30 GMT
Hi,
[del]
>The callback is on anther thread, but I tried to do a raise(SIGSEGV) in
>the server's call back function just to test if the server can catch
>the signal. I found it get and the notExitSigHandler() is called. But
>in real case, which mean when I call the callback using the client's
>invalid object, the server is terminated without catching any signal
>first.
[del]
Depending on the TCP/IP implementation on HPUX, you might get a SIGPIPE
from a broken TCP connection. Try adding this to your signal handler,
but it depends highly upon the underlying ORB which does the network
handling if this will get you further.
Catching signals like SIGSEGV or SIGBUS is of limited value, unless you
can be sure that your thread is either destroyed/cancelled without repeating
the faulty access *and* the variable/member in question is released or
overwritten. But I am repeating myself....
HTH,
Uli
-- Dipl. Inf. Ulrich Teichert|e-mail: Ulrich.Teichert@gmx.de Stormweg 24 |listening to: Suicide Drive (The Deep Eynde) 24539 Neumuenster, Germany|Public Pervert (Interpol) Cauchemar (Opération S)
- Previous message: Sandy: "Re: Why I could not catch the signals on HP_UX?"
- In reply to: Sandy: "Re: Why I could not catch the signals on HP_UX?"
- Next in thread: Sandy: "Re: Why I could not catch the signals on HP_UX?"
- Reply: Sandy: "Re: Why I could not catch the signals on HP_UX?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|