Command caught signal 11 (SEGV)

[John Ferrara]

I have a users switching to an application ID and he getting:

Command caught signal 11 (SEGV)

The system kicks him back to his ID.

Any ideas?

John

[John Palmer]

Hi,

SEGV is a segmentation violation by the program. In other words the program is trying to address some memory that doesn't belong to it.

It's a bug in the program but it may be caused by some external influence such as failing to open a file or having an invalid environment variable for instance.

About the only thing that I can suggest is to obtain the 'tusc' utility from the HP porting centre and use that to trace the system calls that the program makes. It may help you to find out what is going on.

Regards,
John

[Jeff Schussele]

Hi John,

The other scenarios that can kick out SIGSEGV errors is when you've hit a kernel parameter limit like maxtsiz/maxdsiz/maxssiz i.e. you're trying to address MORE memory for text/date/stack space than these will allow.
Another is when a 32-bit app tries to address more memory in total than is allowed (1.75 GB). And a third would be trying to allocate more swap space than is defined.
I suspect something is running out of the application ID's .profile that's doing this. I'd take a look at that .profile - you'll probably find the culprit in there.

HTH,
Jeff

[John Ferrara]

I figured out what the problem was:

The .profile was not owned by the user id.

Odd, but when I cahnged it back to the owner, it worked fine.

Thanks, for the assistance.

John