# Debugger seems broken with Rails 2.3.2

**URL:** <https://www.ruby-forum.com/t/debugger-seems-broken-with-rails-2-3-2/163463>\
**Category:** Rails\
**Created:** [March 20, 2009, 5:03pm UTC](https://www.ruby-forum.com/t/debugger-seems-broken-with-rails-2-3-2/163463 "2009-03-20T17:03:04Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![fipa](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/f/9e8a1a/32.png) [@fipa](https://www.ruby-forum.com/u/fipa)\
**Post date:** [March 20, 2009, 5:03pm UTC](https://www.ruby-forum.com/t/debugger-seems-broken-with-rails-2-3-2/163463/1 "2009-03-20T17:03:04Z")

</div>

With Rails 2.3.2 and ruby-debug 0.10.3 very weird things are happening.  
Am I the only one?

---

<div class="post-metadata">

**Author:** ![fipa](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/f/9e8a1a/32.png) [@fipa](https://www.ruby-forum.com/u/fipa)\
**Post date:** [March 21, 2009, 8:58pm UTC](https://www.ruby-forum.com/t/debugger-seems-broken-with-rails-2-3-2/163463/2 "2009-03-21T20:58:12Z")

</div>

Fernando P. 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,

---

<div class="post-metadata">

**Author:** ![fipa](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/f/9e8a1a/32.png) [@fipa](https://www.ruby-forum.com/u/fipa)\
**Post date:** [March 22, 2009, 6:52pm UTC](https://www.ruby-forum.com/t/debugger-seems-broken-with-rails-2-3-2/163463/3 "2009-03-22T18:52:33Z")

</div>

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 J.

On Mar 21, 3:58 pm, Fernando P. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)

---

<div class="post-metadata">

**Author:** ![fipa](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/f/9e8a1a/32.png) [@fipa](https://www.ruby-forum.com/u/fipa)\
**Post date:** [March 22, 2009, 7:29pm UTC](https://www.ruby-forum.com/t/debugger-seems-broken-with-rails-2-3-2/163463/4 "2009-03-22T19:29:09Z")

</div>

Matt J. 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.

---

<div class="post-metadata">

**Author:** ![fipa](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/f/9e8a1a/32.png) [@fipa](https://www.ruby-forum.com/u/fipa)\
**Post date:** [April 4, 2009, 5:20pm UTC](https://www.ruby-forum.com/t/debugger-seems-broken-with-rails-2-3-2/163463/5 "2009-04-04T17:20:08Z")

</div>

Vladimir R. 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.

---

<div class="post-metadata">

**Author:** ![fipa](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/f/9e8a1a/32.png) [@fipa](https://www.ruby-forum.com/u/fipa)\
**Post date:** [April 4, 2009, 4:42pm UTC](https://www.ruby-forum.com/t/debugger-seems-broken-with-rails-2-3-2/163463/6 "2009-04-04T16:42:45Z")

</div>

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](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.