[PATCH] Fix false positives in tst-pthread-getattr test case

[Siddhesh Poyarekar]

On Tue, 26 Jun 2012 10:53:40 -0400, Carlos wrote:
> It really seems like it's our fault for setting the rlimit to
> something so big?

We don't set the initial rlimit and that is the mystery here since it
should not have come up as unlimited when the system ulimit is small
(8192K in your case). But I guess it does make sense for the test case
to figure out a second threshold that would be reasonable, since it is
also likely that some system may have rlimit_stack explicitly set to
unlimited. __alloca_cutoff should be a good second guess if we get
stacksize as too high. I will change and resubmit once 2.17 opens.

Regards,
Siddhesh