tag:blogger.com,1999:blog-32765306.post115869806096479034..comments2023-02-15T09:11:42.671+00:00Comments on Rich Text: RadRails, all is forgiven!Richard Robertshttp://www.blogger.com/profile/04326338536973407003noreply@blogger.comBlogger34125tag:blogger.com,1999:blog-32765306.post-14634425432903790912008-03-19T11:46:00.000+00:002008-03-19T11:46:00.000+00:00You might want to try Netbeans instead. It works b...You might want to try Netbeans instead. It works beautifully. <BR/><BR/>(I've given up on Radrails/Aptana).<BR/><BR/>Check out these more recent posts:<BR/>http://richtextblog.blogspot.com/2007/09/netbeans-intervenes.html<BR/>http://richtextblog.blogspot.com/2008/03/rails-on-mac-os-x-leopard.htmlRichard Robertshttps://www.blogger.com/profile/04326338536973407003noreply@blogger.comtag:blogger.com,1999:blog-32765306.post-27752519713069577912008-03-19T11:43:00.000+00:002008-03-19T11:43:00.000+00:00Hi,I’ve set up RadRails in Eclipse as specified in...Hi,<BR/><BR/>I’ve set up RadRails in Eclipse as specified in the article, but I always get a java.lang.reflect.InvocationTargetException when launching a debug. Running the same server causes no problems. I’m using webrick, rails 1.2.6, RadRails 1.0.0.2, and ruby 1.8.6.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-32765306.post-9849591915665941232007-03-24T08:12:00.000+00:002007-03-24T08:12:00.000+00:00Hi all, I'm from Aptana, and we've taken over the ...Hi all, I'm from Aptana, and we've taken over the RadRails project. radrails.org is down, so please visit http://www.aptana.com for RadRails downloads.<BR/><BR/>We've published a new build of RadRails based on the RDT nightly. Our next step is automatically configuring ruby-debug. It's a bit rough, but we're working out the edges quickly. Please give it a shot and give us your feedback:<BR/><BR/>http://www.aptana.com/forums/viewtopic.php?t=1145Unknownhttps://www.blogger.com/profile/00025271754401825279noreply@blogger.comtag:blogger.com,1999:blog-32765306.post-14994772079435761522007-03-20T11:04:00.000+00:002007-03-20T11:04:00.000+00:00I have an error after clicking "debug". Could anyo...I have an error after clicking "debug". Could anyone help?<BR/>[2007-03-20 13:57:53] INFO WEBrick 1.3.1<BR/>[2007-03-20 13:57:53] INFO ruby 1.8.5 (2006-08-25) [i386-mswin32]<BR/>[2007-03-20 13:57:53] WARN TCPServer Error: Bad file descriptor - bind(2)Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-32765306.post-85892049562051619692007-03-09T07:32:00.000+00:002007-03-09T07:32:00.000+00:00Fair point about the slowness. I've now changed to...Fair point about the slowness. I've now changed to using Textmate and ruby-debug. See these posts:<BR/><BR/>http://richtextblog.blogspot.com/2007/03/textmate-for-rails.html<BR/><BR/>http://richtextblog.blogspot.com/2007/03/fast-ruby-debugging.htmlRichard Robertshttps://www.blogger.com/profile/04326338536973407003noreply@blogger.comtag:blogger.com,1999:blog-32765306.post-35328960701101701882007-03-08T23:38:00.000+00:002007-03-08T23:38:00.000+00:00Thanks, Rich. Your effort is commended. The positi...Thanks, Rich. Your effort is commended. The positive comments here are for you; the negatives are directed squarely at the junk that is RadRails.<BR/><BR/>This at first <I>seemed</I> to be exactly what I'd wanted, since I am also working in RadRails and had never been able to get anything to debug before. Straight Ruby, yes; Rails, no, because I couldn't figure out what process to debug.<BR/><BR/>Now that I think of it, it actually makes sense -- since the server is just a process running within RadRails, the server itself is the process we need to point at.<BR/><BR/>At any rate, I followed the instruction, and after the usual wrangling with Rails, got it to work.<BR/><BR/>I also experienced the problem with 1.8.4 "requesting to be terminated in an unusual way," but 1.8.4 has never allowed debugging, so I had always reverted to 1.8.2 for debugging before. This was the prompt I needed to upgrade to 1.8.5, and that problem went away.<BR/><BR/>There are two problems now, though. First, the load time for a Rails page to load can now be measured in <B>MINUTES</B>. It's hard to tell whether the app is hung, or just dead slow.<BR/><BR/>Second, the debugger only occasionally stops at breakpoints, or if it does stop at them, it doesn't shift focus to the breakpoint. It's impossible to tell whether the app is hung, just dead slow, or whether it's gone to some breakpoint somewhere and just doesn't feel like showing that. (This is what I'd experienced with debugging Ruby apps before; it's not unique to Rails apps.)<BR/><BR/>So Rich has shown us the right way to go to set up debugging in RadRails. That's a big plus. The big minus is that even when set up right, RadRails just doesn't do debugging very well.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-32765306.post-32426492154973155402007-02-21T17:50:00.000+00:002007-02-21T17:50:00.000+00:00Please look back over the other comments where I h...Please look back over the other comments where I have explained how to check out the variables. In fact, I updated the blog post a couple of months ago to include this info.Richard Robertshttps://www.blogger.com/profile/04326338536973407003noreply@blogger.comtag:blogger.com,1999:blog-32765306.post-46766044248135972862007-02-21T17:28:00.000+00:002007-02-21T17:28:00.000+00:00I can start the debugger, and it stop at my given ...I can start the debugger, and it stop at my given breakpoints, but then I do not see any variables whatsoever. The variables window is just plain empty. Without variables, the debugger is not too useful, so does anyone have an idea?<BR/><BR/>BTW, I had this problem with the debugger not stopping at my breakpoints, too. The solution was simple - there was another server script running at that address and port. Make sure you do not have such a phantom process running when you step into this problem!Metinhttps://www.blogger.com/profile/01675493560427019953noreply@blogger.comtag:blogger.com,1999:blog-32765306.post-89501583593166024362007-02-02T07:41:00.000+00:002007-02-02T07:41:00.000+00:00It is pretty slow isn't it? But it's better than n...It is pretty slow isn't it? But it's better than nothing.<br /><br />The radrails guys say that "Fast Debugging" should be in Radrails 0.8.Richard Robertshttps://www.blogger.com/profile/04326338536973407003noreply@blogger.comtag:blogger.com,1999:blog-32765306.post-10328933997721432962007-02-01T23:31:00.000+00:002007-02-01T23:31:00.000+00:00I got the debugger working for 1.2.1 but boy, is i...I got the debugger working for 1.2.1 but boy, is it slow or what? Whats up with that??ITechiehttps://www.blogger.com/profile/08429112545175450318noreply@blogger.comtag:blogger.com,1999:blog-32765306.post-78203809685236068642007-02-01T07:49:00.000+00:002007-02-01T07:49:00.000+00:00hnr.louder, Sorry - not got any more advice, reall...hnr.louder, Sorry - not got any more advice, really. You may find some tips in the other comments.<br /><br />When I follow the steps in the blog post, it works pretty reliably for me.Richard Robertshttps://www.blogger.com/profile/04326338536973407003noreply@blogger.comtag:blogger.com,1999:blog-32765306.post-73008906107841733632007-02-01T05:05:00.000+00:002007-02-01T05:05:00.000+00:00I've got everything set up per these instructions....I've got everything set up per these instructions. I'm using Ruby 1.8.5 and I'm using the latest Rails and RadRails. <br /><br />When I run the debugger everything starts up but the breakpoints are never hit. Any ideas?Anonymoushttps://www.blogger.com/profile/16711555482619776103noreply@blogger.comtag:blogger.com,1999:blog-32765306.post-10409422303042980722007-01-23T12:47:00.000+00:002007-01-23T12:47:00.000+00:00I had the same problem as many others here, I coul...I had the same problem as many others here, I could not see stopped execution.<br />But if I opened the debug view instead of debug perspective, it worked.Emilhttps://www.blogger.com/profile/12541675073901705144noreply@blogger.comtag:blogger.com,1999:blog-32765306.post-64596182351693697412007-01-10T19:58:00.000+00:002007-01-10T19:58:00.000+00:00Hello caolite. I have the same problem when debug...Hello caolite. I have the same problem when debugging in Mac OSX, but curiously, not in Windows.Richard Robertshttps://www.blogger.com/profile/04326338536973407003noreply@blogger.comtag:blogger.com,1999:blog-32765306.post-2888671323926697672007-01-10T15:53:00.000+00:002007-01-10T15:53:00.000+00:00I've got a problem with terminating. Eclipse claim...I've got a problem with terminating. Eclipse claims to have terminated the debug instance but it's still running and I have to kill it manually at the command line each time.<br /><br />I'm using Linux, probably the problem. Can anyone post if they solve this?Caoiltehttps://www.blogger.com/profile/16640493808944989240noreply@blogger.comtag:blogger.com,1999:blog-32765306.post-27966728859949118562006-12-20T22:12:00.000+00:002006-12-20T22:12:00.000+00:00For people having problems w/ breakpoints not gett...For people having problems w/ breakpoints not getting hit, make sure you're using the debug perspective in Eclipse.<br /><br />At first, I thought I was having that same problem, and that the app was "locking up." It turns out, that my breakpoint was "hit" but I could only see that when in debug perspective. In the default Java perspective, I could see the code and the breakpoint, but not the execution.<br /><br />Hope this helps!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-32765306.post-65388654523633059202006-12-17T17:24:00.000+00:002006-12-17T17:24:00.000+00:00Hello.
Not 100% sure about instant rails, as I do...Hello.<br /><br />Not 100% sure about instant rails, as I don't use it. Give it a go with each and see what happens!Richard Robertshttps://www.blogger.com/profile/04326338536973407003noreply@blogger.comtag:blogger.com,1999:blog-32765306.post-79176590257264588662006-12-17T17:14:00.000+00:002006-12-17T17:14:00.000+00:00Hi,
I am using instanrails. What's the argument fo...Hi,<br />I am using instanrails. What's the argument for -I with Instantrails?<br />Is it,<br />D:\InstantRails\ruby\lib\ruby\gems\1.8\gems\rails-1.1.2\bin<br /><br />or <br /><br />D:\InstantRails\ruby\bin<br /><br />Thanks,<br />Thushantatahttps://www.blogger.com/profile/02800959298947403945noreply@blogger.comtag:blogger.com,1999:blog-32765306.post-56641785913623027452006-12-14T11:54:00.000+00:002006-12-14T11:54:00.000+00:00I was debugging again last night, and it works fin...I was debugging again last night, and it works fine for me. <br /><br />Simply set the breakpoint, start the debug server and go to the DEBUG PERSPECTIVE. It takes a while before the breakpoint is hit as currently debugging in Radrails is quite slow.Richard Robertshttps://www.blogger.com/profile/04326338536973407003noreply@blogger.comtag:blogger.com,1999:blog-32765306.post-23282023318411999852006-12-14T08:56:00.000+00:002006-12-14T08:56:00.000+00:00I have intalled ruby 1.8.5 and now the debug sessi...I have intalled ruby 1.8.5 and now the debug session can start correctly but now I am having the same problem as Rudi; the breakpoints are not being hit. I have set the breakpoints, started the server, started the debug session, enabled the debug view and then nothing happened.<br /><br />If anyone can share any workaround to this problem I would really appreciate it.<br /><br />Thanks!Hugo Arredondohttps://www.blogger.com/profile/15133495971785322832noreply@blogger.comtag:blogger.com,1999:blog-32765306.post-20922887468803021422006-12-14T04:22:00.000+00:002006-12-14T04:22:00.000+00:00Hi!
If I am using Mongrel as my server, could it ...Hi!<br /><br />If I am using Mongrel as my server, could it be possible that running the debugger with webrick can cause the error mentioned by don parish?, <br /><br />"This application has requested the Runtime to terminate it in an unusual way."<br /><br />I am installing ruby 1.8.5 to see if I can overcome this problem<br /><br />ThanksHugo Arredondohttps://www.blogger.com/profile/15133495971785322832noreply@blogger.comtag:blogger.com,1999:blog-32765306.post-58502040023494553742006-11-21T07:46:00.000+00:002006-11-21T07:46:00.000+00:00muralee, I think you're talking about the interpre...muralee, I think you're talking about the interpreter arguments.<br /><br />You need to enter:<br />-I"[path_to_rails]". Note the quotes rather than askerisks. See the screenshot in the blog post for an example.<br /><br />Cheers,<br />Rich.Richard Robertshttps://www.blogger.com/profile/04326338536973407003noreply@blogger.comtag:blogger.com,1999:blog-32765306.post-59304169792360212332006-11-21T03:53:00.000+00:002006-11-21T03:53:00.000+00:00I got the output.But I don't know the parameters d...I got the output.But I don't know the parameters description.Like -I*C:\ruby......*<br /><br />Can you tell the answerAnonymoushttps://www.blogger.com/profile/08741838858086283099noreply@blogger.comtag:blogger.com,1999:blog-32765306.post-40575378764559551662006-11-20T19:52:00.000+00:002006-11-20T19:52:00.000+00:00Hello people. Sorry not responded for a while. I...Hello people. Sorry not responded for a while. I think we've got our wires crossed - my fault, I think. <br /><br />I meant debug "perspective", not "view" (sorry - I'm pretty new to rails). Once you've hit a breakpoint and you go to the debug perspective, you can right click on variables and click "inspect" in the context menu. <br /><br />Hope this helps. I'll update the blog post.Richard Robertshttps://www.blogger.com/profile/04326338536973407003noreply@blogger.comtag:blogger.com,1999:blog-32765306.post-73159159974180486582006-11-20T19:43:00.000+00:002006-11-20T19:43:00.000+00:00I don't mean to question what you're seeing, but j...I don't mean to question what you're seeing, but judging from <a href="http://www.radrails.org/blog/2006/10/2/working-on-rails-debugging">this comment</a>, the variables view should not be populating in v0.7.1. Any chance of screenshots? I can step through my code, but like many here, can't see variable contents, which is rather useless.Anonymousnoreply@blogger.com