mirror/glibc - mirror of git://sourceware.org/git/glibc.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	Fix tst-pthread-getattr test case	Siddhesh Poyarekar	2012-07-28	1	-22/+63
\| \| \| \| \| \|	Get the tst-pthread-getattr fix back with further improvements so that it does not fail on targets that use the user stack to save context.
*	Revert fix to tst-pthread-getattr since it fails on sparc	Siddhesh Poyarekar	2012-07-25	1	-40/+12
\|
*	Fix tst-pthread-getattr test case	Siddhesh Poyarekar	2012-07-20	1	-12/+40
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	In some cases, the compiler would optimize out the call to allocate_and_test and thus result in a false positive for the test case. Another problem was the fact that the compiler could in some cases generate additional shifting of the stack pointer, resulting in alloca moving the stack pointer beyond what is allowed by the rlimit. Hence, accessing the stackaddr returned by pthread_getattr_np is safer than relying on the alloca'd result. Another problem is when RLIMIT may be very large, which may result in violation of other resource limits. Hence we cap the max stack size to 8M for this test.
*	Account for the extra stack size when rlimit is small enough	Siddhesh Poyarekar	2012-06-20	1	-0/+120
	When rlimit is small enough to be used as the stacksize to be returned in pthread_getattr_np, cases where a stack is made executable due to a DSO load get stack size that is larger than what the kernel allows. This is because in such a case the stack size does not account for the pages that have auxv and program arguments. Additionally, the stacksize for the process derived from this should be truncated to align to page size to avoid going beyond rlimit.