Back in Feb & Apr 2003 there was some ruby-talk regarding breakpoints 
not getting set properly, being set but not being "broken" at, problems 
with exactly how the breakpoint should be specified, etc.

I'm trying to look at what the rails-provided WEBrick 
(public/dispatch.servlet) is doing by watching it in the debugger.  I've 
recently posted about a postgresql access problem that i'm trying to 
look into.  I cannot get WEBrick to break at any of the breakpoints i'm 
setting, though.  I've set the following:

(rdb:3) b
Breakpoints:
  1 
/usr/lib/ruby/gems/1.8/gems/activerecord-1.0.0/lib/active_record/connection_adapters/postgresql_adapter.rb:37
  2 ActiveRecord::Base::postgresql_connection
  3 
/usr/lib/ruby/gems/1.8/gems/activerecord-1.0.0/lib/active_record/base.rb:270
  4 
/usr/lib/ruby/gems/1.8/gems/actionpack-0.9.0/lib/action_controller/base.rb:563
  5 
/usr/lib/ruby/gems/1.8/gems/actionpack-0.9.0/lib/action_controller/rescue.rb:68

I picked these based on the stack trace being displayed in my browser on 
the error:

PGError in Album#index
FATAL: IDENT authentication failed for user "postgres"

|/usr/lib/ruby/gems/1.8/gems/activerecord-1.0.0/lib/active_record/connection_adapters/postgresql_adapter.rb:37:in `connect'
/usr/lib/ruby/gems/1.8/gems/activerecord-1.0.0/lib/active_record/connection_adapters/postgresql_adapter.rb:37:in `postgresql_connection'
/usr/lib/ruby/gems/1.8/gems/activerecord-1.0.0/lib/active_record/connection_adapters/abstract_adapter.rb:117:in `send'
/usr/lib/ruby/gems/1.8/gems/activerecord-1.0.0/lib/active_record/connection_adapters/abstract_adapter.rb:117:in `connection='
/usr/lib/ruby/gems/1.8/gems/activerecord-1.0.0/lib/active_record/connection_adapters/abstract_adapter.rb:81:in `retrieve_connection'
/usr/lib/ruby/gems/1.8/gems/activerecord-1.0.0/lib/active_record/base.rb:172:in `connection'
/usr/lib/ruby/gems/1.8/gems/activerecord-1.0.0/lib/active_record/base.rb:276:in `find_by_sql'
/usr/lib/ruby/gems/1.8/gems/activerecord-1.0.0/lib/active_record/base.rb:270:in `find_all'
/usr/lib/ruby/gems/1.8/gems/actionpack-0.9.0/lib/action_controller/scaffolding.rb:103:in `list'
/usr/lib/ruby/gems/1.8/gems/actionpack-0.9.0/lib/action_controller/scaffolding.rb:96:in `index'
/usr/lib/ruby/gems/1.8/gems/actionpack-0.9.0/lib/action_controller/base.rb:563:in `send'
/usr/lib/ruby/gems/1.8/gems/actionpack-0.9.0/lib/action_controller/base.rb:563:in `perform_action_without_filters'
/usr/lib/ruby/gems/1.8/gems/actionpack-0.9.0/lib/action_controller/filters.rb:236:in `perform_action_without_benchmark'
/usr/lib/ruby/gems/1.8/gems/actionpack-0.9.0/lib/action_controller/benchmarking.rb:30:in `perform_action_without_rescue'
/usr/lib/ruby/gems/1.8/gems/actionpack-0.9.0/lib/action_controller/benchmarking.rb:30:in `measure'
/usr/lib/ruby/gems/1.8/gems/actionpack-0.9.0/lib/action_controller/benchmarking.rb:30:in `perform_action_without_rescue'
/usr/lib/ruby/gems/1.8/gems/actionpack-0.9.0/lib/action_controller/rescue.rb:68:in `perform_action'
/usr/lib/ruby/gems/1.8/gems/actionpack-0.9.0/lib/action_controller/base.rb:254:in `process'
/usr/lib/ruby/gems/1.8/gems/actionpack-0.9.0/lib/action_controller/base.rb:235:in `process'
/usr/lib/ruby/gems/1.8/gems/rails-0.8.0/lib/dispatcher.rb:35:in `dispatch'
/public/dispatch.rb:10
/public/dispatch.rb:1:in `load'
/public/dispatch.rb:1

-:7

Is this trace being generated from another process entirely?
Unless breakpoints in debug.rb are broken, i can't think of why i never hit any of the ones i set.

|