I am having a problem with the debugger. When I edit a hello world program ( to keep it simple) and execute the debugger, it brings up ubygems.rb and stops on the first line which is require rubygems.rb. At this point I can hit step in followed by step out, or just hit step over, and it brings me to my program. I think I have an idea of why this is happening, but it is very confusing to a new user and it is not documented anywhere. I was wondering: 1. Is this behavior normal? 2. Is this a result of me having installed ruby one click, than deleting freeride, then installing new version of freeride. 3. Is there anywhere to document these kind of common problems that people might run into during install. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/freeride-users/attachments/20051017/f8437c4a/attachment.htm -------------- next part -------------- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.12.2/139 - Release Date: 10/17/2005
bill hunter wrote:> I am having a problem with the debugger. When I edit a hello world > program ( to keep it simple) and execute the debugger, it brings up > ubygems.rb and stops on the first line which is require rubygems.rb. At > this point I can hit step in followed by step out, or just hit step > over, and it brings me to my program. I think I have an idea of why this > is happening, but it is very confusing to a new user and it is not > documented anywhere. > > I was wondering: > 1. Is this behavior normal? > 2. Is this a result of me having installed ruby one click, than deleting > freeride, then installing new version of freeride. > 3. Is there anywhere to document these kind of common problems that > people might run into during install. > >Bill there must be a combination of factor that explains your problem because I haven''t heard of anything like this yet. 1. The behavior is not normal 2. I don;t think this could be the problem 3. As I said it''s not that common Can you do 4 things for me: a) post the exact ruby program you are debugging b) try and see if it changes anything if you explicitely specify the path to the c) is there any message showing up when the debugger stops (e.g en exception message) d) tell me if you are you using the latest CVS version or 0.9.4? Laurent
----- Original Message ----- From: "Laurent Julliard" <laurent at moldus.org> To: <freeride-users at rubyforge.org> Sent: Tuesday, October 18, 2005 7:57 AM Subject: Re: [FR-users] Problem with debugger> bill hunter wrote: >> I am having a problem with the debugger. When I edit a hello world >> program ( to keep it simple) and execute the debugger, it brings up >> ubygems.rb and stops on the first line which is require rubygems.rb. At >> this point I can hit step in followed by step out, or just hit step >> over, and it brings me to my program. I think I have an idea of why this >> is happening, but it is very confusing to a new user and it is not >> documented anywhere. >> >> I was wondering: >> 1. Is this behavior normal? >> 2. Is this a result of me having installed ruby one click, than deleting >> freeride, then installing new version of freeride. >> 3. Is there anywhere to document these kind of common problems that >> people might run into during install. >> >> > > Bill there must be a combination of factor that explains your problem > because I haven''t heard of anything like this yet. > > 1. The behavior is not normal > 2. I don;t think this could be the problem > 3. As I said it''s not that common > > Can you do 4 things for me: > > a) post the exact ruby program you are debugging > b) try and see if it changes anything if you explicitely specify the > path to the > c) is there any message showing up when the debugger stops (e.g en > exception message) > d) tell me if you are you using the latest CVS version or 0.9.4? > > Laurenta) It doesn''t seem to matter what the program is so I will give you this trivial one that I am using to track this problem: 5.times{ print"hello world\n" } b) path to the ....? I''ll give you the paths for some stuff and hope I get what you are looking for bullseye icon target: C:\Programs\ruby\FreeRIDE\run.bat bullseye icon start directory: C:\Programs\ruby\FreeRIDE c) Debugger process started (druby://hp64:1285,process id 1520) d) help about yields: This is FreeRide version 0.9.4 I am running windows XP on an athlon 64, with a standard Freeride install. Environment variable that might be related : Path = %SystemRoot%\system32;%SystemRoot%;c:\System32\Wbem;c:\programs\ruby\bin RUBYOPT = rubygems Let me know if there is anything else you want to know. I am obviously able to work around this problem, but would like to pursue it too improve the usability of freeRide for new users. -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.12.4/142 - Release Date: 10/18/2005
bill hunter wrote:> I am running windows XP on an athlon 64, with a standard Freeride install. > Environment variable that might be related : > Path = > %SystemRoot%\system32;%SystemRoot%;c:\System32\Wbem;c:\programs\ruby\bin > RUBYOPT = rubygems >Ok so that''s the RUBYOPT = rubygems that is causing the problem. Well actually it''s not really a bug. By default, the FR debugger stops on the first executable line of your script. Since you require the "ubygems" module, ruby loads it first and start the execution here so this is where the debugger stops. We could fix the problem by stopping the debugger when it reaches the first executable line of the script itself but it migh also be interesting to step into the modules that are included from the command line. One day it could be your own modules and you may want to debug in there as well. ANybody has an opinion about what is th best thing to do here? Laurent
On 10/19/05, Laurent Julliard <laurent at moldus.org> wrote:> > bill hunter wrote: > > > I am running windows XP on an athlon 64, with a standard Freeride > install. > > Environment variable that might be related : > > Path > > %SystemRoot%\system32;%SystemRoot%;c:\System32\Wbem;c:\programs\ruby\bin > > RUBYOPT = rubygems > > > > Ok so that''s the RUBYOPT = rubygems that is causing the problem. Well > actually it''s not really a bug. By default, the FR debugger stops on > the first executable line of your script. Since you require the > "ubygems" module, ruby loads it first and start the execution here so > this is where the debugger stops. > > We could fix the problem by stopping the debugger when it reaches the > first executable line of the script itself but it migh also be > interesting to step into the modules that are included from the > command line. One day it could be your own modules and you may want to > debug in there as well. > > ANybody has an opinion about what is th best thing to do here?I think it should stay the way it is. Its important to know that other modules are executing and deliberately hiding that fact is dangerous. Curt -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/freeride-users/attachments/20051019/adec3abb/attachment.htm
Curt Hibbs <curt.hibbs at gmail.com> wrote: On 10/19/05, Laurent Julliard <laurent at moldus.org> wrote: bill hunter wrote:> I am running windows XP on an athlon 64, with a standard Freeride install. > Environment variable that might be related : > Path > %SystemRoot%\system32;%SystemRoot%;c:\System32\Wbem;c:\programs\ruby\bin > RUBYOPT = rubygems >Ok so that''s the RUBYOPT = rubygems that is causing the problem. Well actually it''s not really a bug. By default, the FR debugger stops on the first executable line of your script. Since you require the "ubygems" module, ruby loads it first and start the execution here so this is where the debugger stops. We could fix the problem by stopping the debugger when it reaches the first executable line of the script itself but it migh also be interesting to step into the modules that are included from the command line. One day it could be your own modules and you may want to debug in there as well. ANybody has an opinion about what is th best thing to do here? I think it should stay the way it is. Its important to know that other modules are executing and deliberately hiding that fact is dangerous. Curt It would not be other modules that your script included, just the one module, ubygems.rb, that the ruby.exe pulled in behind your back. That said, if you decide to not change it, than a simple heads up in the install notes would be nice. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/freeride-users/attachments/20051019/e4518fcd/attachment.htm