Forum: Ruby on Rails debugger seems broken with Rails 2.3.2

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
059ed46172a087063ce26250e44c8627?d=identicon&s=25 Fernando Perez (fernando)
on 2009-03-20 17:03
With Rails 2.3.2 and ruby-debug 0.10.3 very weird things are happening.
Am I the only one?
059ed46172a087063ce26250e44c8627?d=identicon&s=25 Fernando Perez (fernando)
on 2009-03-21 20:58
Fernando Perez wrote:
> With Rails 2.3.2 and ruby-debug 0.10.3 very weird things are happening.
> Am I the only one?

Here is one of the weird behavior: in development mode, if I edit a
Model, I sometimes notice that the code doesn't get reload when I issue
the 'list' command in the debugger. Therefore I bang my head not
understanding why my edits don't make any change.

Therefore I have to ctrl+c and relaunch Thin. Anyone else ran in this
problem previously?


Best regards,
6883e5ef03484d4fcef507d7b4f1d243?d=identicon&s=25 Matt Jones (Guest)
on 2009-03-22 18:52
(Received via mailing list)
Did that *ever* work? Development mode reloading only works between
requests. Ruby-debug may also be caching its own copy of the source
somewhere.

--Matt Jones

On Mar 21, 3:58 pm, Fernando Perez <rails-mailing-l...@andreas-s.net>
059ed46172a087063ce26250e44c8627?d=identicon&s=25 Fernando Perez (fernando)
on 2009-03-22 19:29
Matt Jones wrote:
> Did that *ever* work? Development mode reloading only works between
> requests. Ruby-debug may also be caching its own copy of the source
> somewhere.

I think it happens when I open another terminal and use script/console.
Well I wasn't able to clearly identify the cause.

Another weird behavior, is that when the debugger kicks in, sometimes I
can directly access classes and objects without having to go into irb (I
think that applies when debugger is in a model), sometimes I need to
enter irb.

Another one: when entering irb, I sometimes see lot's of error/warning
messages, and the request carries on as if the breakpoint didn't exist.
If I reissue the request and enter irb, the second time the request
won't carry on.
Fce8e97a4f558dcdd7d6a64f02c493a6?d=identicon&s=25 Vladimir Rybas (Guest)
on 2009-04-04 16:42
(Received via mailing list)
I've got the same problems

I'm running as regular
> $ ruby script/server --debugger
reach the break point
> (rdb:5)
trying to run irb
> (rdb:5) irb
and
> INTERNAL ERROR!!! Unrecognized switch: -debugger
>...
Full trace here:
http://pastie.org/436603.txt

But if you run debugger with RAILS_GEM_VERSION 2.2.2 or 2.1.2,
everything works fine.
irb by itself and script/console works fine under 2.3.2

Ubuntu Linux 8.10
kernel 2.6.27-7-generic
ruby 1.8.7 (2008-08-11 patchlevel 72) [i486-linux]

Temporary solution: run debugger through
> $ rdebug ./script/server
Have to push "c" after starting up

Anyway, better than nothing.
059ed46172a087063ce26250e44c8627?d=identicon&s=25 Fernando Perez (fernando)
on 2009-04-04 17:20
Vladimir Rybas wrote:
> I've got the same problems

I saw somewhere that irb in debugger is an "experimental feature", so
we'll have to deal with it. Anyway I can do 99% of my debugging simply
by using pp to figure how things will get evaluated and the state of the
variables.
This topic is locked and can not be replied to.