search

pry / pry-stack_explorer

Walk the stack in a Pry session
Other
455 stars 28 forks source link

segfault on ruby 1.9.3p448 #16

Closed heartpunk closed 4 years ago

heartpunk commented 11 years ago

Unfortunately, it's in a private repo to which I don't have IP rights. What information could I try to get you that might help in building a repro? I don't have time to figure out the whole repro on my own, but I'm happy to do what I can to get the relevant info.

kyrylo commented 11 years ago

First of all, are you sure you're using the latest version of the gem? What are you trying to do?

heartpunk commented 11 years ago

Latest version of pry, I didn't constrain the pry-stack_explorer version. Unfortunately, that bit of my gemfile is blown away now, so I can't be sure which it happened with.

Trying binding.pry in the context of a factory/rspec with the stack explorer loaded. segfaulted before showing me the pry prompt.

kyrylo commented 11 years ago

So putting binding.pry into a factory definition results in a segfault?

heartpunk commented 11 years ago

Specifically it was in an after(:build) callback, but it also happened in the context of a before(:all) in rspec.

heartpunk commented 11 years ago

Maybe it comes down to a conflict with another loaded gem with extensions (or one without)?

kyrylo commented 11 years ago

It is possible. Do you use any other Pry plugins apart from pry-rails?

heartpunk commented 11 years ago

Not even pry-rails

kyrylo commented 11 years ago

OK, your application is not a Rails application, is it?

heartpunk commented 11 years ago

It is rails! Rails 3.2.13.

kyrylo commented 11 years ago

So how do you run Pry? You're supposed to include the pry-rails gem in your Gemfile. See https://github.com/pry/pry/wiki/Setting-up-Rails-or-Heroku-to-use-Pry#wiki-pry_rails

heartpunk commented 11 years ago

Just binding.pry with gem 'pry' in the Gemfile.

heartpunk commented 11 years ago

Oh, I don't really want to use pry everywhere. I set it up for specific instances because it's nicer than debugger. If that's all that pry-rails does, I'm not after it.

kyrylo commented 11 years ago

Oh, I see. That should be fine. Does the segfault occur if you put binding.pry inside a test?

heartpunk commented 11 years ago

Haven't tried that! Lemme check.

heartpunk commented 11 years ago

yes. took the time to filter the sensitive stuff outta this stack trace for you.

kyrylo commented 11 years ago

Thanks. We'll see what we can do…

heartpunk commented 11 years ago

:thumbsup:

doudou commented 11 years ago

I can confirm the crashing behaviour. Don't have time to isolate the problem right now, but I'll try to do it in the next weeks.