My recommendation is you to print the values on the console to track them at "run-time", I prefer to use this technique more than use the integrated debugger, since you can follow up the overall outcome without start/stops. Some people don't like it, but I find it very useful.
On Fri, May 1, 2009 at 5:20 PM, richard terry <[email protected]> wrote: > If one puts in a breakpoint, and is stepping through the code one line at a > time to check values of variables etc, is there any way or re-setting to a > line in the same subroutine prior to the current line you have stopped on. > > I've found sometimes I'm trying to find a bug, and I put in multiple break > points so that I can skip from one to another, and then want to check > something in the middle that I've gone past, but have to stop the entire > program and start again. > > perhaps I'm using this tool wrongly. > > Thanks. > > ------------------------------------------------------------------------------ > Register Now & Save for Velocity, the Web Performance & Operations > Conference from O'Reilly Media. Velocity features a full day of > expert-led, hands-on workshops and two days of sessions from industry > leaders in dedicated Performance & Operations tracks. Use code vel09scf > and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf > _______________________________________________ > Gambas-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/gambas-user > ------------------------------------------------------------------------------ Register Now & Save for Velocity, the Web Performance & Operations Conference from O'Reilly Media. Velocity features a full day of expert-led, hands-on workshops and two days of sessions from industry leaders in dedicated Performance & Operations tracks. Use code vel09scf and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf _______________________________________________ Gambas-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/gambas-user
