-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regularly segfaults on ruby-1.9.3-p385 #14
Comments
it would be interesting to the diff b/w p187 and the previous patchlevel, im guessing it doesnt' segv on the previous one? |
also, i can't get it to segfault on ruby 2.0, can you confirm this too? (rc2) |
FWIW I've not been able to get it to segfault on 2.0 since the update. |
I've had mostly segmentation faults as well on Ruby 1.9.3-p192 and 1.9.3-p392 in Mac OS X 10.8.2. I've had no faults running rspec since I removed binding_of_caller from my Gemfile. Version 0.7.1. |
I"m also getting this quite reliably (3/5 runs with rspec). Ruby versions: 1.9.3-p125 and 1.9.3-p396 |
With this gem I get segfaults when running rspec / jasmine:ci in 1.9.3-p392, without it, none. |
@donnfelker @cmaujean @ConradIrwin Do you have any indication of what triggers the segfault? A simple repro would really help a lot in this case. |
@badosu: I think it's some kind of use-after-free bug ( A while back I started trying to trace this through, and the segfault was somewhere deep inside Getting into the realms of superstition, at one point we thought we had a link between binding stacks that included top-level blocks (which are pervasive in rspec) and segfaults; but I'm not convinced that was any more than coincidence. |
Same deal here, I can get a reliable segfault using p429 on https://github.com/SquareSquash/ruby/tree/segfault ( C backtrace (excerpt):
Ruby backtrace (excerpt):
|
Thank you! I am gonna check it out! |
@ConradIrwin Just tested the repro you`ve shown in master and it worked. Do you still have this issue using master? |
@badosu only on ruby 1.9.3-p385. on 1.9.3-p392 it works. I'm not sure whether it's worth investigating on -p385; it might be best to use @RISCfuture's example which is apparently reliable on latest ruby (though I think the cause will be the same). |
I get a SegFault using Ruby 1.9.3-p392 when I run my specs. |
@ConradIrwin I tested your repo on 1.9.3-p385 as well. Strange. @RISCfuture I tested yours in 1.8.7-p371 and 1.9.3-p385 in the branch segfault. You meant 1.9.3-p429? I could not install it with rvm, will compile it later. Maybe it is specific to OSX? |
Maybe you're right, I'm in OS X. |
@ConradIrwin , @RISCfuture Are you on OSX? |
yes |
yep |
Ok, I will try to test it on a OSX box then, thanks! |
I'm able to reproduce this on CentOS 6.4 and ruby 1.9.3-p448 with binding_of_caller v0.7.4. Just a data point. |
Interestingly, if I run:
I get the SegFault. However, if I run:
I do not! Here's my traceback (from OSX), in case you're interested:
I'm willing to help track this down, if you want it. |
I'm having the same issue with ruby 1.9.3-p392, rails 3.2.13, rspec 2.13.1 osx 10.8.4 |
I'm having this problem on Ubuntu 13.04, while my other computer with ubunto 12.04 LTS does not have this problem. |
Could you share any info on how to reproduce this? It is so frustrating... I just tried a lot of rubies, including 193-p392, 192-p290, 193-p448 on lspace and SquareSquash. @bomberby I am using 13.04 as well. Maybe it could be related with some installed lib? |
@badosu I re-ran my test with ruby-p185 and lspace's branch. It doesn't seem to segfault... I've updated my operating system (which shouldn't have much effect), and I'm probably using a different version of bundler (which might have some effect), but otherwise everything should be the same as before. I even tried setting |
@docwhat, the latest version of I'm using Arch Linux x64. I tried to reproduce this bug (without luck) on these rubies:
LSpace showed no segfaults. |
@bomberby, is your Ubuntu 13.04 32-bit or 64-bit? |
Both are 64-bit |
@plindelauf when you say removed from your gem file do mean a line from the Gemfile it's self or do mean remove it from your bundle? |
I've found this issue intermittently with If I use the version in |
On Thu, 17 Oct 2013 12:22:40 -0700
Thanks for the information. However, what do you use in order to |
Closing this since ruby 1.9.3 is well past its end of life. |
To reproduce:
Will segfault reliably.
The text was updated successfully, but these errors were encountered: