[#78633] ruby/spec needs help from CRuby committers — Benoit Daloze <eregontp@...>
Currently, ruby/spec is maintained mostly by individuals and enjoys the
13 messages
2016/12/13
[#78963] Re: ruby/spec needs help from CRuby committers
— Urabe Shyouhei <shyouhei@...>
2017/01/04
I did ask attendees of last developer meeting to join this
[#78642] Re: ruby/spec needs help from CRuby committers
— Eric Wong <normalperson@...>
2016/12/14
Benoit Daloze <eregontp@gmail.com> wrote:
[ruby-core:78488] [Ruby trunk Feature#13006] backtrace of thread killer
From:
akostadinov@...
Date:
2016-12-04 17:43:29 UTC
List:
ruby-core #78488
Issue #13006 has been reported by Aleksandar Kostadinov. ---------------------------------------- Feature #13006: backtrace of thread killer https://bugs.ruby-lang.org/issues/13006 * Author: Aleksandar Kostadinov * Status: Open * Priority: Normal * Assignee: ---------------------------------------- Hello, I am right now having difficulties to understand why one thread I have is dead. Seems been killed by something (rails/puma). But there is no way I can see to understand what and why did it. That's why I'm proposing a new feature. This would be `Thread#kill` should record a backtrace at time of call and record it somewhere in the thread object so that later calling `Thread#killer_trace` would show what performed this call. -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>