[#84867] [Ruby trunk Bug#14357] thread_safe tests suite segfaults — v.ondruch@...

Issue #14357 has been reported by vo.x (Vit Ondruch).

11 messages 2018/01/15
[#85364] Re: [Ruby trunk Bug#14357] thread_safe tests suite segfaults — Eric Wong <normalperson@...> 2018/02/03

v.ondruch@tiscali.cz wrote:

[#84980] [Ruby trunk Feature#13618][Assigned] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid — hsbt@...

Issue #13618 has been updated by hsbt (Hiroshi SHIBATA).

10 messages 2018/01/23
[#85012] Re: [Ruby trunk Feature#13618][Assigned] [PATCH] auto fiber schedule for rb_wait_for_single_fd and rb_waitpid — Eric Wong <normalperson@...> 2018/01/23

hsbt@ruby-lang.org wrote:

[ruby-core:84756] Re: [ruby-cvs:68887] mame:r61706 (trunk): Explicit failure in VM_CHECK_MODE when failing to create timer thread

From: Eric Wong <normalperson@...>
Date: 2018-01-09 07:19:54 UTC
List: ruby-core #84756
mame@ruby-lang.org wrote:
>   https://svn.ruby-lang.org/cgi-bin/viewvc.cgi?view=revision&revision=61706
> 
>   Log:
>     Explicit failure in VM_CHECK_MODE when failing to create timer thread
>     
>     "warning: pthread_create failed for timer: Resource temporarily
>     unavailable, scheduling broken" still occurs randomly.  This change will
>     allow us to debug the issue.

But you put the assertion for pthread_attr_init failure in your
commit, was that intentional?  I don't think EAGAIN on
pthread_create is avoidable if the system is overloaded.

Maybe pthread_attr_setstacksize fails on some systems, do you
have any info on the system?  Is it Linux?

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>

In This Thread

Prev Next