On Mon, 2006-10-16 at 12:00 -0500, Chakarat Skawratananond wrote:
>
> Currently, I always set HUGETLB_VERBOSE to 99 in order to get all the
> debug message.
> And the understanding now is that by setting it to 1, we will get less
> detail.
>
> Wouldn't it be more intuitive if we set to 100 to
Currently, I always set HUGETLB_VERBOSE
to 99 in order to get all the debug message.
And the understanding now is that by
setting it to 1, we will get less detail.
Wouldn't it be more intuitive if we
set to 100 to get more detailed if application segfaults ?
--
On 16.10.2006 [10:08:29 -0500], Bill Buros wrote:
>
>
> Steve Fox wrote:
>
> >docs: Add information on HUGETLB_DEBUG
> >
> >
> just an observation...on SLES 10, one very common application
> segfault is due to ulimit -s being defaulted to 8192. Not sure
> if the debug messages spit t
On 16.10.2006 [13:12:44 +1000], David Gibson wrote:
> On Fri, Oct 13, 2006 at 12:45:44PM -0700, Nishanth Aravamudan wrote:
> > On 11.10.2006 [13:53:18 +1000], David Gibson wrote:
> > > A couple of questions about the mlock testcase added in commit
> > > ff2f5343e4a4e2d2e62173d557a7e5952cfa7733.
> >
Steve Fox wrote:
>docs: Add information on HUGETLB_DEBUG
>
>
just an observation...on SLES 10, one very common application
segfault is due to ulimit -s being defaulted to 8192. Not sure if
the debug messages spit this out, but we always tell our users to set
the stack to unlimited
docs: Add information on HUGETLB_DEBUG
Signed-off-by: Steve Fox <[EMAIL PROTECTED]>
---
diff --git a/HOWTO b/HOWTO
index 2c0c47a..4a587c3 100644
--- a/HOWTO
+++ b/HOWTO
@@ -319,6 +319,9 @@ libhugetlbfs:
Specify the path to the hugetlbfs mount point
HUGETLB_SHARE
