The Artima Developer Community
Sponsored Link

Ruby Buzz Forum
The Call Stack - Debugging Ruby 'Backwards'

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Huw Collingbourne

Posts: 1254
Nickname: huw
Registered: Nov, 2006

Huw Collingbourne is Director of Technology for the Ruby In Steel IDE
The Call Stack - Debugging Ruby 'Backwards' Posted: Mar 15, 2007 7:29 AM
Reply to this message Reply

This post originated from an RSS feed registered with Ruby Buzz by Huw Collingbourne.
Original Post: The Call Stack - Debugging Ruby 'Backwards'
Feed Title: SapphireSteel Software
Feed URL: http://www.sapphiresteel.com/spip.php?page=backend&id_rubrique=1
Feed Description: Discussion of Ruby, Flex and the Ruby In Steel and Amethyst/Flex IDEs for Visual Studio.
Latest Ruby Buzz Posts
Latest Ruby Buzz Posts by Huw Collingbourne
Latest Posts From SapphireSteel Software

Advertisement
The Call Stack gives you a great way to ‘trace backwards' through the execution of your Ruby programs. Whereas a breakpoint shows you where you are at a given moment in the life of your program, the call stack shows you where you have been.
Each time you step into a new method with the debugger, a new entry is added to the call stack . So, if you enter method x, the call stack pane shows x along with (optionally) some other information such as the name of the source file and (...)

Read: The Call Stack - Debugging Ruby 'Backwards'

Topic: That Stupid Thing I Wrote The Other Day, part 1 Previous Topic   Next Topic Topic: Palm and Mac Users

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use