On Tuesday, September 1, 2015 at 8:21:06 AM UTC+2, BobN wrote: > > ------------------------- > "One step at a time > > Once the debugger is paused, you can continue execution one line at a > time. This allows you to see exactly how variables and objects are effected > when a particular line is executed. > > You can also choose to step execution for more than one line. From the > context menu, choose "Run to this Line" to continue execution until it > passes through the line you clicked." > ---------------------- > Not much help! > > That seems more line a sales pitch than documentation on using a program. >
It is exactly that. The documentation is available at https://getfirebug.com/wiki, which is also linked to from the FAQ. > Does the text "...continue execution until it passes through the line you > clicked." Mean the line on which you set a checkpoint? If so, why not say > that and if it means something else, why not make it clear? > > The contextual menu for the JavaScript source display panel simply is > another way to perform the same functions as the icons - it has the same > text for each option as the icon tooltip. > > Is there any real help available? > See https://getfirebug.com/wiki/index.php/Script_Panel#Execution_Control_Buttons . > Is there such a thing a a Help File or a set of Help HTML pages? > Press F1 while you're within Firebug and you get to the FAQ. Click Firebug menu (the button with the Firebug icon at the top left in Firebug) > *Firebug Online* > *Documentation...* and you get to the wiki mentioned above. I need details in what each option for "stepping" in debugger does. For > example, which icon means execute next statement? Is it "Step Into"? If so, > why not say Next Statement? > > "Stepping into" something conjures up thoughts of stepping into a > function, not "stepping" into the next statement????? > You're right. *Step Into* steps into a function. When you're not at a function statement, it works like Step Over by stepping to the next statement. > The other "step" actions - what do they each mean? > > You don't have to teach me how to debug - have been doing it for 42+ > years, sometimes using methods that you would consider primitive. I just > need to know the nomenclature for Firebug. > Note that the nomenclature in Firebug matches the one of pretty much every other debugger out there. See e.g. Visual Studio <https://msdn.microsoft.com/en-US/library/y740d9d3.aspx>, NetBeans <https://netbeans.org/kb/docs/php/debugging.html#work>, Eclipse <http://agile.csc.ncsu.edu/SEMaterials/tutorials/eclipse-debugger/>, or the Firefox DevTools <https://developer.mozilla.org/en-US/docs/Tools/Debugger/How_to/Step_through_code> . With the many years of debugging experience you have, it should be easy for you to grasp what Step Over/Into/Out means. Or at least it should have been easy for you to find the related documentation <http://lmgtfy.com/?q=firebug+step+over+into+out>. Sebastian PS: Keeping posts concise attracts more people to read them and avoids TL;DR comments. -- You received this message because you are subscribed to the Google Groups "Firebug" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/firebug. To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/9bad7727-4f99-4b64-934b-03553f4b2a33%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
