[omniORB] FW: [EXTERNAL]: Re: Segfault from libomniOrb

[Krishnamohan, Srivathsan]

Thanks for the reply. We already have the full stack trace of where libomniORB crashes. Every time it crashes in the same place with same stack trace. We do not know how to trigger it, so cannot debug using gdb. How will recompiling with -g help? It might prevent the crash from happening.

There are multiple c++ applications which dynamically link to libomniOrb . When segfault happens in libomniOrb, I can see as many as 10 processes terminating. In the /var/log/messages , sometimes, I see messages such as:

ServerApp[26286]: segfault at 9e496 ip 000000000009e496 sp 00007fff9eed9e78 error 14 in ServerApp_6.2.008.0.1C2[400000+c0a000]
ServerApp2_6.2.[31338]: segfault at 9e496 ip 000000000009e496 sp 00007ffc11cad678 error 14 in ServerApp2_6.2.008.0.2C1[400000+1552000]
....
When multiple applications crash, they all show the same instruction pointer. Sometimes, I see this message too:

[136523.109657] traps: ServiceApp_6.2.[6406] trap stack segment ip:7f473e8758c4 sp:7ffcc54424d0 error:0 in libomniORB4.so.2[7f473e787000+1b5000]traps:


CONFIDENTIALITY NOTICE: This email transmission, and any documents, files or previous email messages attached to it, may contain confidential information. If you are not the intended recipient or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this message is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately destroy the original transmission and its attachments without reading them or saving them to disk. Email communications may be monitored by KLA as permitted by applicable law and regulations. For more information, read our Privacy Policy at www.kla.com/privacy-policy.<http://www.kla.com/privacy-policy> Thank you.