Project

General

Profile

Actions
Copy link

Backport #10243

closed

segmentation fail during a debug session with pry

Added by komidore64 (Adam Price) over 9 years ago. Updated almost 5 years ago.

Status:
Closed
Assignee:
-
[ruby-core:65048]

Files

Download all files
ruby-segfault.txt (427 KB) ruby-segfault.txt komidore64 (Adam Price), 09/15/2014 02:35 PM
rails-segfault-bundle-list.txt (4.59 KB) rails-segfault-bundle-list.txt komidore64 (Adam Price), 09/15/2014 02:35 PM
Actions
Copy link
 #1 [ruby-core:65081]

Updated by usa (Usaku NAKAMURA) over 9 years ago

Unfortunately, the necessary information is lacking this log. (It is not your fault.)
This is not a problem of ruby itself, in my intuition.

Can you always reproduce this problem?
And, can you make a small code to reproduce this?

Actions
Copy link
 #2 [ruby-core:65082]

Updated by usa (Usaku NAKAMURA) over 9 years ago

  • Status changed from Open to Feedback

I forgot to say an important thing.
We have already ended the normal bug fix phase of the mentenance of ruby 1.9.3.
This means that if we find the cause of the SEGV, we will not release the fix for 1.9.3.
You should try to update ruby to 2.1 or 2.0.0.

Actions
Copy link
 #3

Updated by jeremyevans0 (Jeremy Evans) almost 5 years ago

  • Status changed from Feedback to Closed
Actions
Copy link

Also available in: Atom PDF

Like0
Like0Like0Like0