[omniORB] Signals being caught by omniORB?

[Jayanth Venkatraj]

Hey Duncan,

We are trying to force a core dump on our application which is connected to the ORB. The application is running on a RHEL 6(Linux) box, and we are using omniORB-4.1.4.

We usually use kill -6 <pid> (-SIGABRT) or kill -11 <pid> (-SIGSEGV) to force the core generation. But, kill -3 doesn't have any effect, and on kill -11, we get this error:

terminate called after throwing an instance of 'omni_thread_fatal'
EVServices: ./../../../rw/db/dbref.h:251: T *RWDBCountedRef<T>::operator->() const [with T = RWDBHandleImp]: Assertion `(impl_) != 0' failed.
/evaluate/ev_dev87/shl/StartProcess.sh[69]: wait: 36309: Killed
Tue Dec 10 15:30:42 EST 2013 Exited EVServices, pid=36309, with ERROR returncode=265 signal=SIGKILL


We want to know if there is some code in omniORB, that prevents the core generation.

Thanks,
Jay Venkatraj
Credit Management Solutions, Inc.
7142 Columbia Gateway Drive, Suite 100
Columbia, MD 21046
[phone] ext 8181

"The information contained in this email message may be privileged and/or confidential and protected from disclosure under applicable law. It is intended only for the individual to whom or entity to which it is addressed as shown at the beginning of the message. If the reader of this message is not the intended recipient, or if the employee or agent responsible for delivering the message is not an employee or agent of the intended recipient, you are hereby notified that any review, dissemination, distribution, use, or copying of this message is strictly prohibited. If you have received this message in error, please notify us immediately by return email and permanently delete this message and your reply to the extent it includes this message. Any views or opinions presented in this message or attachments are those of the author and do not necessarily represent those of the Company. All emails and attachments sent and received are subject to monitoring, reading and archival by the Company."

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20131210/279d6acb/attachment.html>

[Duncan Grisby]

On Tue, 2013-12-10 at 20:33 +0000, Jayanth Venkatraj wrote:

[...]

Post by Jayanth Venkatraj
We usually use kill -6 <pid> (-SIGABRT) or kill -11 <pid> (-SIGSEGV)
to force the core generation. But, kill -3 doesn?t have any effect,
terminate called after throwing an instance of 'omni_thread_fatal'
EVServices: ./../../../rw/db/dbref.h:251: T
Assertion `(impl_) != 0' failed.

[...]

Post by Jayanth Venkatraj
We want to know if there is some code in omniORB, that prevents the core generation.

No, there's nothing in omniORB that does that. The only signal it masks
is SIGPIPE, which is triggered when a socket is closed.

Duncan.