- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Problem with PTHREAD_STACK_MIN
Operating System - HP-UX
1754324
Members
2634
Online
108813
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2011 12:36 AM
05-12-2011 12:36 AM
Re: Problem with PTHREAD_STACK_MIN
There is no bug in pthread_detach. This was simply caused by an indirect setjmp call through a Ruby's rb_raise in a thread leading to various run-time failures. Squeezing this rb_raise made Ruby behave much better.
Got a little problem with pthread_cond_timedwait. It looks like that the maximum acceptable delay is 874800000 seconds under HP-UX 11iv3.
About PTHREAD_STACK_MIN, no support contract => no problem report to HP.
Now the latest Ruby is available on HP-UX. It has already really interested two Chinese people. And this is what I really do care about.
Got a little problem with pthread_cond_timedwait. It looks like that the maximum acceptable delay is 874800000 seconds under HP-UX 11iv3.
About PTHREAD_STACK_MIN, no support contract => no problem report to HP.
Now the latest Ruby is available on HP-UX. It has already really interested two Chinese people. And this is what I really do care about.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2011 03:15 AM
05-12-2011 03:15 AM
Re: Problem with PTHREAD_STACK_MIN
Hi:
> It has already really interested two Chinese people. And this is what I really do care about.
Who cares what nationality is interested? As a global community, why not simply say "...has really interested TWO PEOPLE".
...JRF...
> It has already really interested two Chinese people. And this is what I really do care about.
Who cares what nationality is interested? As a global community, why not simply say "...has really interested TWO PEOPLE".
...JRF...
- « Previous
-
- 1
- 2
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP