SIGSEGV, in user mode, [caught], partial siginfo Siginfo: si_code: I_NONEXIST, faulting addr

[Steven Gillard_2]

A tusc trace is usually not useful in debugging a SIGSEGV - it generally occurs in user mode when you attempt to access a memory address that does not belong to your process. Your application should have generated a core file, which you can use with gdb / wdb to obtain a stack trace. If you've compiled with -g you can go right back to the source file and line where the faulting address was accessed.

Cheers,
Steve

[Roger Baptiste]

hi,

If you are getting a SIGSEGV violation, the possible problems could be in the kernel setting of maxdsiz parameter . Also have a look at the maxssiz param. (this is for maximum data and stack segments).

Check the configured swap through swapinfo -mt.

HTH
raj