Solution : https://service.sap.com/sap/support/notes/350167 (SAP Service marketplace login required)
Summary :
This SAP Note addresses the occurrence of signals 11 (SIGSEGV, Segmentation Violation) and 10 (SIGBUS, Bus error), predominately caused by improper parameter settings or application bugs. SIGSEGV indicates an invalid memory access, usually due to application error. The document underscores that, despite commonly being an application-level issue, SIGSEGV has rarely originated from SunOS itself in recent years. Recommendations include verifying parameter settings like shmmax and ensuring adequate OS swap space. For debugging, ensuring core dumps are enabled and using tools like 'adb' or 'pstack' are recommended, alongside checking parameter and memory configurations against SAP guidelines.
Key words :
`exe'$ adb core core file = core -- program `exe' sigsegv 11, prerequisites wrong parameter settings application bug solution description, elf 32-bit msb core file sparc version 1, xterm / # ps pid tty time cmd 18565 pts/11 0, 18562 dumped # adb /usr/openwin/bin/xterm core, + tu02->abap/heap_area_dia / abap/heap_area_nondiaboth values, process = st02->detail analysis menu-> storage->, # adb /sapmnt/agf/exe/disp+work, 18562 -- program ``/usr/openwin/bin/xterm'', /3 memory pool sizesin 64 bit environments
Related Notes :
| 666203 | corrupted application dumps under Solaris |
| 300464 | Shared Memory Parameters in Solaris |
| 103747 | Performance: Parameter recommendations as of Release 4.0 |
| 97497 | Memory Management Parameter (3.0/3.1) |