tag:blogger.com,1999:blog-2958021377042600373.post2726113633219119729..comments2007-03-28T08:47:43.508-07:00JESiihttp://www.blogger.com/profile/03694926683464859622noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-2958021377042600373.post-1412479857376432732007-03-28T08:47:00.000-07:002007-03-28T08:47:00.000-07:00Just found an extensive discussion on the Rails wiki on <A HREF="http://wiki.rubyonrails.com/rails/pages/HowtoDebugWithBreakpoint" REL="nofollow"><BR/>HowToDebugWithBreakpoint</A>. Haven't tried it out, but it looks very interesting.JESiihttp://www.blogger.com/profile/03694926683464859622noreply@blogger.comtag:blogger.com,1999:blog-2958021377042600373.post-33260037783774034282007-03-28T08:23:00.000-07:002007-03-28T08:23:00.000-07:00Thanks, Florian... I posted this question on <A HREF="http://groups.google.com/group/rubyonrails-talk/browse_thread/thread/99dbc6bd331f039d/082aa18c376cd417?lnk=gst&q=breakpoint&rnum=1&hl=en#082aa18c376cd417" REL="nofollow">Ruby on Rails: Talk</A> and got some great feedback. You're correct that the rdebug appreoach seems to be the preferred method: Kent Sibilev gave me the scoop:<BR/><BR/>C:\rails-app>rdebug ./script/server <BR/><BR/>and you're good to go!JESiihttp://www.blogger.com/profile/03694926683464859622noreply@blogger.comtag:blogger.com,1999:blog-2958021377042600373.post-76014046039342815022007-03-25T13:18:00.000-07:002007-03-25T13:18:00.000-07:00ruby-debug uses a custom client. I believie it is called rdebug or something. As soon as it is connected you will probably want to enter 'irb'.<BR/><BR/>Another solution might be to continue using ruby-breakpoint, but with Breakpoint.breakpoint(nil, binding) instead of breakpoint().<BR/><BR/>Hope that helps!Florian Großhttp://www.blogger.com/profile/05128769452612477118noreply@blogger.com