Understanding Step Over in Rails Debugging, seems like funny things happening

View: New views
3 Messages — Rating Filter:   Alert me  

Understanding Step Over in Rails Debugging, seems like funny things happening

by Chris Kutler :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Here is what I believe the definition of Step Over is:

Step Over. Executes one source line of a program. If the line is a method call, executes the entire method then stops.

Often times, when debugging a test, Step Over (in the actual controller class) takes me into the method call.

For example, it stops at this breakpointed line
    @calendar = Calendar.find(params[:id])
I click Step Over and it stops at the following line in filters.rb
        if controller.send!(:performed?)
Step Out takes me to this line in filters.rb
      def call(controller, &block)

Is that a bug or is there a reason for this.

Sometimes when this happens, I try Step Out to get back but I don't seem to be able to. so I click Continue. When I do that, I end up having to click Continue a lot ,with it stopping in a lot of places deep down that didn't have break points. Eventually, I hit some wall and the class simply stops running.



Re: Understanding Step Over in Rails Debugging, seems like funny things happening

by Martin Krauskopf :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Chris Kutler wrote:

> Here is what I believe the definition of Step Over is:
>
>     Step Over. Executes one source line of a program. If the line is a
>     method call, executes the entire method then stops.
>
>
> Often times, when debugging a test, Step Over (in the actual controller
> class) takes me into the method call.
>
> For example, it stops at this breakpointed line
>     @calendar = Calendar.find(params[:id])
> I click Step Over and it stops at the following line in filters.rb
>         if controller.send!(:performed?)
> Step Out takes me to this line in filters.rb
>       def call(controller, &block)
>
> Is that a bug or is there a reason for this.

The stepping is driven by debugger backend. Please file a bug against
ruby/debugger with details (platform, server) and ideally step to
reproduce if possible.

I've been debugging MRI/Mongrel few hours yesterday without problems.
Also quickly tried your case now without being able to reproduce.

Thanks,
        m.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...


Re: Understanding Step Over in Rails Debugging, seems like funny things happening

by Chris Kutler :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

http://www.netbeans.org/issues/show_bug.cgi?id=145611

I changed it to an issue about continue. I think I am wrong about the
step over thing.

Martin Krauskopf wrote:

> Chris Kutler wrote:
>> Here is what I believe the definition of Step Over is:
>>
>>     Step Over. Executes one source line of a program. If the line is a
>>     method call, executes the entire method then stops.
>>
>>
>> Often times, when debugging a test, Step Over (in the actual
>> controller class) takes me into the method call.
>>
>> For example, it stops at this breakpointed line
>>     @calendar = Calendar.find(params[:id])
>> I click Step Over and it stops at the following line in filters.rb
>>         if controller.send!(:performed?)
>> Step Out takes me to this line in filters.rb
>>       def call(controller, &block)
>>
>> Is that a bug or is there a reason for this.
>
> The stepping is driven by debugger backend. Please file a bug against
> ruby/debugger with details (platform, server) and ideally step to
> reproduce if possible.
>
> I've been debugging MRI/Mongrel few hours yesterday without problems.
> Also quickly tried your case now without being able to reproduce.
>
> Thanks,
>     m.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...