Closed melcher closed 11 years ago
You shouldn't have a require or debugger in your Gemfile. Rather, you should place this in the specific line you're debugging
I experienced the segfault adding the debugger line to a model method, also in my model tests. Since this is in a large project I thought it may be due to some other plugin we're using, and attempted to isolate the issue and produce a more useful backtrace by loading the debugger first and running it. This produced the same exception. If this plugin won't work when required/run from a gemfile I'll try to reproduce with a minimal project, but may not have time to put something together anytime soon. Was hoping there was a known issue or other fix. Thanks,
Ok. I'm closing this and can reopen if/when you provide a sample app. I did notice in your stacktrace that the first line comes from a .so file which is odd considering everything else is .bundle. You may have a gcc setup issue.
This started with seg-faults being thrown within the application - i tried to narrow it down by including 'debugger' and using as the first thing in my Gemfile, and it's segfaulting on the same line in debugger:
debugger-1.3.0/lib/ruby-debug-base.rb:213: [BUG] Segmentation fault
Thoughts?$ ruby --version ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-darwin11.4.2]
$ rails --version Rails 3.2.11
My Gemfile starts with:
Full segfault trace: