On Tue, Mar 20, 2007 at 01:43:57PM -0700, Bart Smaalders wrote:
> Turns out the limit command doesn't display the actual
> limit size above some pretty nominal values, but the
> limit command seems to work up to 2GB or so.
Yes, the thing that's interesting here is that his process is either
somehow not honouring the limit or the limit is being reset along the
way:
FFFFFD7FE9DFC000 8 8 8 - rwx-- ld.so.1
FFFFFD7FFC419000 59292 59292 59292 - rw--- [ stack ]
> FFFFFD7FFC419000-FFFFFD7FE9DFC000+(0t59292<<0t10)=X
16004000
So the effective limit appears to be about 352MB. Normally, a 64-bit
process (such as yours) will yield this when run with an unlimited
stack size.
...
00007FFFFFFFB000 8 8 8 - rwx-- ld.so.1
FFFFFD7FFFDFD000 12 12 12 - rw--- [ stack ]
which leaves oodles. So...is some fortran library or openmp-related
generated code resetting the limits somewhere along the way? Sounds
like a job for truss and/or DTrace...
--
Keith M Wesolowski "Sir, we're surrounded!"
FishWorks "Excellent; we can attack in any direction!"
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
