On 9/10/2012 11:13 AM, Carlos O'Donell wrote:
On 9/9/2012 6:24 PM, John David Anglin wrote:
>On 9-Sep-12, at 4:23 PM, John David Anglin wrote:
>
>>It seems to me this must be a kernel bug:
>
>Nope, it's a problem with guard page allocation in openjdk.
>It assumes stack grows down.
Yes, that's wrong:-)
If you allocate your own stacks then glibc can't setup guard
pages for you since it violates some POSIX constraints.
I need to study the situation in more detail but what I found is openjdk
initially allocates a fairly large stack with pthread_attr_setstacksize,
then it mucks with this region setting up guard pages, etc. This goes
seriously wrong on parisc and the initial thread is only left with a stack
which is 4096 bytes.
I disabled guard pages and the build went a lot further, but died again
due to what appears to be another stack related issue. If this package
is to work again, it's going to need significant porting to fix the stack
handling. I think there was a parisc patch at one time but I think it
has been removed...
If I understand correctly, we have on parisc a guard region followed
by TLS stuff at the top of stack. I assume that the stack size allocated
with pthread_attr_setstacksize is fully available to the user.
Dave
--
John David Anglin dave.anglin@xxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe linux-parisc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
