ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
* [ruby-core:61553] [Backport200 - Backport #9649] [Open] Segfault running thread_safe torture tests under Ruby 2.0
       [not found] <redmine.issue-9649.20140317125458@ruby-lang.org>
@ 2014-03-17 12:54 ` headius
  2014-03-17 20:57   ` [ruby-core:61566] " Eric Wong
  2014-03-17 21:03 ` [ruby-core:61567] [Backport200 - Backport #9649] " normalperson
                   ` (5 subsequent siblings)
  6 siblings, 1 reply; 8+ messages in thread
From: headius @ 2014-03-17 12:54 UTC (permalink / raw)
  To: ruby-core

Issue #9649 has been reported by Charles Nutter.

----------------------------------------
Backport #9649: Segfault running thread_safe torture tests under Ruby 2.0
https://bugs.ruby-lang.org/issues/9649

* Author: Charles Nutter
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
We received the following report on the thread_safe project: https://github.com/headius/thread_safe/issues/32

It does not appear that any extension code is involved in the backtrace, so I believe the most likely scenario is that the problem lies in MRI.

I have not received any reports of segfaults other than this one.



-- 
http://bugs.ruby-lang.org/

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [ruby-core:61566] Re: [Backport200 - Backport #9649] [Open] Segfault running thread_safe torture tests under Ruby 2.0
  2014-03-17 12:54 ` [ruby-core:61553] [Backport200 - Backport #9649] [Open] Segfault running thread_safe torture tests under Ruby 2.0 headius
@ 2014-03-17 20:57   ` Eric Wong
  0 siblings, 0 replies; 8+ messages in thread
From: Eric Wong @ 2014-03-17 20:57 UTC (permalink / raw)
  To: Ruby developers

This is fixed in Ruby 2.0.0 p451, seems related to
https://bugs.ruby-lang.org/issues/9178

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [ruby-core:61567] [Backport200 - Backport #9649] Segfault running thread_safe torture tests under Ruby 2.0
       [not found] <redmine.issue-9649.20140317125458@ruby-lang.org>
  2014-03-17 12:54 ` [ruby-core:61553] [Backport200 - Backport #9649] [Open] Segfault running thread_safe torture tests under Ruby 2.0 headius
@ 2014-03-17 21:03 ` normalperson
  2014-04-30  6:05 ` [ruby-core:62236] [Backport200 - Backport #9649] [Closed] " usa
                   ` (4 subsequent siblings)
  6 siblings, 0 replies; 8+ messages in thread
From: normalperson @ 2014-03-17 21:03 UTC (permalink / raw)
  To: ruby-core

Issue #9649 has been updated by Eric Wong.


 This is fixed in Ruby 2.0.0 p451, seems related to
 https://bugs.ruby-lang.org/issues/9178

----------------------------------------
Backport #9649: Segfault running thread_safe torture tests under Ruby 2.0
https://bugs.ruby-lang.org/issues/9649#change-45850

* Author: Charles Nutter
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
We received the following report on the thread_safe project: https://github.com/headius/thread_safe/issues/32

It does not appear that any extension code is involved in the backtrace, so I believe the most likely scenario is that the problem lies in MRI.

I have not received any reports of segfaults other than this one.



-- 
httsp://bugs.ruby-lang.org/

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [ruby-core:62236] [Backport200 - Backport #9649] [Closed] Segfault running thread_safe torture tests under Ruby 2.0
       [not found] <redmine.issue-9649.20140317125458@ruby-lang.org>
  2014-03-17 12:54 ` [ruby-core:61553] [Backport200 - Backport #9649] [Open] Segfault running thread_safe torture tests under Ruby 2.0 headius
  2014-03-17 21:03 ` [ruby-core:61567] [Backport200 - Backport #9649] " normalperson
@ 2014-04-30  6:05 ` usa
  2015-07-10  8:36 ` [ruby-core:69930] [Backport200 - Backport #9649] " hans
                   ` (3 subsequent siblings)
  6 siblings, 0 replies; 8+ messages in thread
From: usa @ 2014-04-30  6:05 UTC (permalink / raw)
  To: ruby-core

Issue #9649 has been updated by Usaku NAKAMURA.

Status changed from Open to Closed

see r44150.

----------------------------------------
Backport #9649: Segfault running thread_safe torture tests under Ruby 2.0
https://bugs.ruby-lang.org/issues/9649#change-46385

* Author: Charles Nutter
* Status: Closed
* Priority: Normal
* Assignee: 
----------------------------------------
We received the following report on the thread_safe project: https://github.com/headius/thread_safe/issues/32

It does not appear that any extension code is involved in the backtrace, so I believe the most likely scenario is that the problem lies in MRI.

I have not received any reports of segfaults other than this one.



-- 
https://bugs.ruby-lang.org/

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [ruby-core:69930] [Backport200 - Backport #9649] Segfault running thread_safe torture tests under Ruby 2.0
       [not found] <redmine.issue-9649.20140317125458@ruby-lang.org>
                   ` (2 preceding siblings ...)
  2014-04-30  6:05 ` [ruby-core:62236] [Backport200 - Backport #9649] [Closed] " usa
@ 2015-07-10  8:36 ` hans
  2015-07-10  8:55 ` [ruby-core:69933] " usa
                   ` (2 subsequent siblings)
  6 siblings, 0 replies; 8+ messages in thread
From: hans @ 2015-07-10  8:36 UTC (permalink / raw)
  To: ruby-core

Issue #9649 has been updated by Hans de Graaff.


I can still reproduce this issue with ruby 2.0.0p645 (2015-04-13 revision 50299) [x86_64-linux] and thread_safe 0.3.5. The error is not consistent, so it may take a couple of runs to actually hit the problem.

See https://github.com/ruby-concurrency/thread_safe/issues/21 for a new bug report on this including backtrace.

----------------------------------------
Backport #9649: Segfault running thread_safe torture tests under Ruby 2.0
https://bugs.ruby-lang.org/issues/9649#change-53353

* Author: Charles Nutter
* Status: Closed
* Priority: Normal
* Assignee: 
----------------------------------------
We received the following report on the thread_safe project: https://github.com/headius/thread_safe/issues/32

It does not appear that any extension code is involved in the backtrace, so I believe the most likely scenario is that the problem lies in MRI.

I have not received any reports of segfaults other than this one.



-- 
https://bugs.ruby-lang.org/

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [ruby-core:69933] [Backport200 - Backport #9649] Segfault running thread_safe torture tests under Ruby 2.0
       [not found] <redmine.issue-9649.20140317125458@ruby-lang.org>
                   ` (3 preceding siblings ...)
  2015-07-10  8:36 ` [ruby-core:69930] [Backport200 - Backport #9649] " hans
@ 2015-07-10  8:55 ` usa
  2015-07-27 19:34 ` [ruby-core:70134] " hans
  2015-07-27 19:57 ` [ruby-core:70136] " hans
  6 siblings, 0 replies; 8+ messages in thread
From: usa @ 2015-07-10  8:55 UTC (permalink / raw)
  To: ruby-core

Issue #9649 has been updated by Usaku NAKAMURA.


The normal maintenance phase of ruby 2.0.0 is already ended.
Try ruby 2.1 or 2.2.

----------------------------------------
Backport #9649: Segfault running thread_safe torture tests under Ruby 2.0
https://bugs.ruby-lang.org/issues/9649#change-53355

* Author: Charles Nutter
* Status: Closed
* Priority: Normal
* Assignee: 
----------------------------------------
We received the following report on the thread_safe project: https://github.com/headius/thread_safe/issues/32

It does not appear that any extension code is involved in the backtrace, so I believe the most likely scenario is that the problem lies in MRI.

I have not received any reports of segfaults other than this one.



-- 
https://bugs.ruby-lang.org/

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [ruby-core:70134] [Backport200 - Backport #9649] Segfault running thread_safe torture tests under Ruby 2.0
       [not found] <redmine.issue-9649.20140317125458@ruby-lang.org>
                   ` (4 preceding siblings ...)
  2015-07-10  8:55 ` [ruby-core:69933] " usa
@ 2015-07-27 19:34 ` hans
  2015-07-27 19:57 ` [ruby-core:70136] " hans
  6 siblings, 0 replies; 8+ messages in thread
From: hans @ 2015-07-27 19:34 UTC (permalink / raw)
  To: ruby-core

Issue #9649 has been updated by Hans de Graaff.

File threadsafe-ruby21.txt added

I can also reproduce this with ruby 2.1 (note that it may take a couple of test runs of the threadsafe test suite to trigger this).

----------------------------------------
Backport #9649: Segfault running thread_safe torture tests under Ruby 2.0
https://bugs.ruby-lang.org/issues/9649#change-53565

* Author: Charles Nutter
* Status: Closed
* Priority: Normal
* Assignee: 
----------------------------------------
We received the following report on the thread_safe project: https://github.com/headius/thread_safe/issues/32

It does not appear that any extension code is involved in the backtrace, so I believe the most likely scenario is that the problem lies in MRI.

I have not received any reports of segfaults other than this one.

---Files--------------------------------
threadsafe-ruby21.txt (32.8 KB)


-- 
https://bugs.ruby-lang.org/

^ permalink raw reply	[flat|nested] 8+ messages in thread

* [ruby-core:70136] [Backport200 - Backport #9649] Segfault running thread_safe torture tests under Ruby 2.0
       [not found] <redmine.issue-9649.20140317125458@ruby-lang.org>
                   ` (5 preceding siblings ...)
  2015-07-27 19:34 ` [ruby-core:70134] " hans
@ 2015-07-27 19:57 ` hans
  6 siblings, 0 replies; 8+ messages in thread
From: hans @ 2015-07-27 19:57 UTC (permalink / raw)
  To: ruby-core

Issue #9649 has been updated by Hans de Graaff.


So far I have not been able to reproduce this with ruby 2.2.2p95 (2015-04-13 revision 50295) [x86_64-linux]


----------------------------------------
Backport #9649: Segfault running thread_safe torture tests under Ruby 2.0
https://bugs.ruby-lang.org/issues/9649#change-53567

* Author: Charles Nutter
* Status: Closed
* Priority: Normal
* Assignee: 
----------------------------------------
We received the following report on the thread_safe project: https://github.com/headius/thread_safe/issues/32

It does not appear that any extension code is involved in the backtrace, so I believe the most likely scenario is that the problem lies in MRI.

I have not received any reports of segfaults other than this one.

---Files--------------------------------
threadsafe-ruby21.txt (32.8 KB)


-- 
https://bugs.ruby-lang.org/

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2015-07-27 19:26 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <redmine.issue-9649.20140317125458@ruby-lang.org>
2014-03-17 12:54 ` [ruby-core:61553] [Backport200 - Backport #9649] [Open] Segfault running thread_safe torture tests under Ruby 2.0 headius
2014-03-17 20:57   ` [ruby-core:61566] " Eric Wong
2014-03-17 21:03 ` [ruby-core:61567] [Backport200 - Backport #9649] " normalperson
2014-04-30  6:05 ` [ruby-core:62236] [Backport200 - Backport #9649] [Closed] " usa
2015-07-10  8:36 ` [ruby-core:69930] [Backport200 - Backport #9649] " hans
2015-07-10  8:55 ` [ruby-core:69933] " usa
2015-07-27 19:34 ` [ruby-core:70134] " hans
2015-07-27 19:57 ` [ruby-core:70136] " hans

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).