cldwalker/debugger

Can't get break to work

JESii opened this issue · 4 comments

Started Rails with debugger:

rdebug Rails s

Added breakpoint:

(rdb:1) break /home/jseidel/.rvm/gems/ruby-1.9.3-p327@rails3212/bundler/gems/active_scaffold-7172b114e082/lib/active_scaffold/actions/update.rb:14
Breakpoint 1 file /home/jseidel/.rvm/gems/ruby-1.9.3-p327@rails3212/bundler/gems/active_scaffold-7172b114e082/lib/active_scaffold/actions/update.rb, line 14

Crashed, referencing the above breakpoint line:

NoMethodError (undefined method `each' for nil:NilClass):
/home/jseidel/.rvm/gems/ruby-1.9.3-p327@rails3212/bundler/gems/active_scaffold-7172b114e082/lib/active_scaffold/attribute_params.rb:43:in `update_record_from_params'
/home/jseidel/.rvm/gems/ruby-1.9.3-p327@rails3212/bundler/gems/active_scaffold-7172b114e082/lib/active_scaffold/actions/update.rb:91:in `block in update_save'
activerecord (3.2.12) lib/active_record/connection_adapters/abstract/database_statements.rb:192:in `transaction'
activerecord (3.2.12) lib/active_record/transactions.rb:208:in `transaction'
/home/jseidel/.rvm/gems/ruby-1.9.3-p327@rails3212/bundler/gems/active_scaffold-7172b114e082/lib/active_scaffold/actions/update.rb:90:in `update_save'
/home/jseidel/.rvm/gems/ruby-1.9.3-p327@rails3212/bundler/gems/active_scaffold-7172b114e082/lib/active_scaffold/actions/update.rb:84:in `do_update'
/home/jseidel/.rvm/gems/ruby-1.9.3-p327@rails3212/bundler/gems/active_scaffold-7172b114e082/lib/active_scaffold/actions/update.rb:14:in `update'
actionpack (3.2.12) lib/action_controller/metal/implicit_render.rb:4:in `send_action'
actionpack (3.2.12) lib/abstract_controller/base.rb:167:in `process_action'
actionpack (3.2.12) lib/action_controller/metal/rendering.rb:10:in `process_action'

I was expecting to get control in .../active_scaffold/actions/update.rb at line 14 as specified in the breakpoint. What am I doing wrong? FYI, I had problems with the old rdebug19 module as well...

Thanks for reporting your issue! This is one of my 11 active issues. Use that link to check how soon your issue will be answered. Cheers.

Thanks; let me know if you need any testing or other help.

It looks like it's crapping out before it gets to the breakpoint. If debugger were failing I would expect to see a stacktrace pointing to debugger's internals. I'd recommend wrapping the failing line in a begin and rescue to see what is nil and why. This may be an activescaffold bug.

Closing. I can reopen when you've looked into my suggestion.