------art_115611_16488517.1180123979379
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 5/25/07, Jorge Domenico Bucaran Romano <jbucaran / gmail.com> wrote:
>
>
> (rdb:1) b c:\users\jbucaran\desktop\demo2.rb
> C:/Program Files/Ruby/lib/ruby/site_ruby/1.8/ubygems.rb:10:compile error
> C:/Program Files/Ruby/lib/ruby/site_ruby/1.8/ubygems.rb:10: syntax
> error, unexpe
> cted $undefined, expecting tSTRING_CONTENT or tSTRING_DBEG or
> tSTRING_DVAR or tS
> TRING_END
> c:\users\jbucaran\desktop\demo2
>    ^
> (rdb:1) Set breakpoint 1 at c:\users\jbucaran\desktop\demo2.rb:1
> C:/Program Files/Ruby/lib/ruby/site_ruby/1.8/ubygems.rb:10: warning:
> parenthesiz
> e argument(s) for future version
> C:/Program Files/Ruby/lib/ruby/site_ruby/1.8/ubygems.rb:10:compile error
> C:/Program Files/Ruby/lib/ruby/site_ruby/1.8/ubygems.rb:10: syntax
> error, unexpe
> cted tIDENTIFIER, expecting $end
> Set breakpoint 1 at c:\users\jbucaran\desktop\demo2.rb:1
>                    ^
> (rdb:1)


It looks to me like the debugger is getting confused by the colon after C
drive.
The usage for the 'b' command: b[reak] [file:|class:]<line|method>
See? You can specify a file and then a colon and the class etc. but the
debugger is not expecting a colon in the path.

Try just "b 1" to set a breakpoint on line 1.

Les

------art_115611_16488517.1180123979379--