Partha,
In my last post, I said:
> I think, if you see a SIGSEGV because of hitting a
> kernel limit, you should contact HP representative
> and file a defect.
I think it came out a little different than I intended
it to. So let me clarify that. There are only few
conditions, like a program overflowing the stack,
when SIGSEGV can happen because of inadequate
value of kernel parameter. This is because the
program needs a stack larger than 'maxssiz'. You
might have hit that in your case if there is no
problem with your code (can be confirmed by following A. Clay Stephenson's suggestion of
compiling with -g option). If the problem is in your
code, you will hit SIGSEGV even if you increase
'maxssiz'. In general, SIGSEGV can happen because
of 2 conditions, 1) illegal address being referenced
and 2) invalid permission for the address.
Hope this is clear now.
- Biswajit
:-)
