debugging over loops

Hi Joe,

 

There are a few ways to get out of a loop.  The best way is to just let the loop run.  To do that select the space on your code you want to jump to right click and select: “run to here”

 

 

That will take you to the place you clicked on in your code.

 

There is another trick, loops usually have an index.  This is Smalltalk after all.  In the case above I just selected this code and selected “Debug it”

 

1 to: 100 do: [:i | Transcript show: i asString].

Transcript show: 'done'.

 

While in the outer content evaluating the loop, select i change the value to 100 hit accept and “bobs your uncle” the loop is done. 

 

Ok so a bit of a hack but I’ve used it to skip over some processing and since you are debugging and know what you are doing it should be fine.

 

 

Proceed is just continue and stop debugging.

 

Restart will stop debugging at the selected method and restart that method from the beginning.

 

Into goes into the execution of the next method and shows you what it does

 

Over executes the next message and moves over it to the next message

 

Through steps you through a block of code, so if you are about to execute a block, this steps you through that block

 

Full Stack increases the number of levels you see in the upper panel.  That normally shows you a subset of the execution stack.  Full stack will show you the rest of the stack that called this method.

 

Where is useful if you click around a method during debugging.  It will highlight the code at its execution point.  You can also just select the stack method again to do the same thing.

 

Tally well is supposed to Tally selected code.  Ignore Tally.  If you want to tally something do it outside a debugger.

 

Hope that helps!

 

All the best,

 

Ron Teitelbaum

Head Of Engineering

3d Immersive Collaboration Consulting

[hidden email]

Follow Me On Twitter: @RonTeitelbaum

www.3dicc.com

https://www.google.com/+3dicc

 

 

 

> -----Original Message-----

> From: [hidden email] [mailto:[hidden email]

> [hidden email]] On Behalf Of Joseph J Alotta

> Sent: Friday, May 30, 2014 11:55 AM

> To: [hidden email]

> Subject: [Newbies] debugging over loops

>

> Greetings,

>

> How do I debug over loops?  I tried using the "over" step and the "through"

> step, but that just keeps me inside the loop.

>

> I don't know what the other buttons do, like "tally".  Is there somewhere

> that explains this?

>

> Sincerely,

>

> Joe.

>

>

>

> _______________________________________________

> Beginners mailing list

> [hidden email]

> http://lists.squeakfoundation.org/mailman/listinfo/beginners

 

_______________________________________________
Beginners mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/beginners

Hi,

I don't see the 'run to here' option in any menu.

What version of Squeak do you run ?

Cheers,

Karl

On Fri, May 30, 2014 at 6:35 PM, Ron Teitelbaum <[hidden email]> wrote:

Hi Joe,

 

There are a few ways to get out of a loop.  The best way is to just let the loop run.  To do that select the space on your code you want to jump to right click and select: “run to here”

 

 

That will take you to the place you clicked on in your code.

 

There is another trick, loops usually have an index.  This is Smalltalk after all.  In the case above I just selected this code and selected “Debug it”

 

1 to: 100 do: [:i | Transcript show: i asString].

Transcript show: 'done'.

 

While in the outer content evaluating the loop, select i change the value to 100 hit accept and “bobs your uncle” the loop is done. 

 

Ok so a bit of a hack but I’ve used it to skip over some processing and since you are debugging and know what you are doing it should be fine.

 

 

Proceed is just continue and stop debugging.

 

Restart will stop debugging at the selected method and restart that method from the beginning.

 

Into goes into the execution of the next method and shows you what it does

 

Over executes the next message and moves over it to the next message

 

Through steps you through a block of code, so if you are about to execute a block, this steps you through that block

 

Full Stack increases the number of levels you see in the upper panel.  That normally shows you a subset of the execution stack.  Full stack will show you the rest of the stack that called this method.

 

Where is useful if you click around a method during debugging.  It will highlight the code at its execution point.  You can also just select the stack method again to do the same thing.

 

Tally well is supposed to Tally selected code.  Ignore Tally.  If you want to tally something do it outside a debugger.

 

Hope that helps!

 

All the best,

 

Ron Teitelbaum

Head Of Engineering

3d Immersive Collaboration Consulting

[hidden email]

Follow Me On Twitter: @RonTeitelbaum

www.3dicc.com

https://www.google.com/+3dicc

 

 

 

> -----Original Message-----

> From: [hidden email] [mailto:[hidden email]

> [hidden email]] On Behalf Of Joseph J Alotta

> Sent: Friday, May 30, 2014 11:55 AM

> To: [hidden email]

> Subject: [Newbies] debugging over loops

>

> Greetings,

>

> How do I debug over loops?  I tried using the "over" step and the "through"

> step, but that just keeps me inside the loop.

>

> I don't know what the other buttons do, like "tally".  Is there somewhere

> that explains this?

>

> Sincerely,

>

> Joe.

>

>

>

> _______________________________________________

> Beginners mailing list

> [hidden email]

> http://lists.squeakfoundation.org/mailman/listinfo/beginners

 

_______________________________________________
Beginners mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/beginners

I found it in the method pane of the debugger.

Sorry for the noise

Cheers,

Karl

On Sun, Jun 1, 2014 at 7:51 PM, karl ramberg <[hidden email]> wrote:

Hi,

I don't see the 'run to here' option in any menu.

What version of Squeak do you run ?

Cheers,

Karl

On Fri, May 30, 2014 at 6:35 PM, Ron Teitelbaum <[hidden email]> wrote:

Hi Joe,

 

There are a few ways to get out of a loop.  The best way is to just let the loop run.  To do that select the space on your code you want to jump to right click and select: “run to here”

 

 

That will take you to the place you clicked on in your code.

 

There is another trick, loops usually have an index.  This is Smalltalk after all.  In the case above I just selected this code and selected “Debug it”

 

1 to: 100 do: [:i | Transcript show: i asString].

Transcript show: 'done'.

 

While in the outer content evaluating the loop, select i change the value to 100 hit accept and “bobs your uncle” the loop is done. 

 

Ok so a bit of a hack but I’ve used it to skip over some processing and since you are debugging and know what you are doing it should be fine.

 

 

Proceed is just continue and stop debugging.

 

Restart will stop debugging at the selected method and restart that method from the beginning.

 

Into goes into the execution of the next method and shows you what it does

 

Over executes the next message and moves over it to the next message

 

Through steps you through a block of code, so if you are about to execute a block, this steps you through that block

 

Full Stack increases the number of levels you see in the upper panel.  That normally shows you a subset of the execution stack.  Full stack will show you the rest of the stack that called this method.

 

Where is useful if you click around a method during debugging.  It will highlight the code at its execution point.  You can also just select the stack method again to do the same thing.

 

Tally well is supposed to Tally selected code.  Ignore Tally.  If you want to tally something do it outside a debugger.

 

Hope that helps!

 

All the best,

 

Ron Teitelbaum

Head Of Engineering

3d Immersive Collaboration Consulting

[hidden email]

Follow Me On Twitter: @RonTeitelbaum

www.3dicc.com

https://www.google.com/+3dicc

 

 

 

> -----Original Message-----

> From: [hidden email] [mailto:[hidden email]

> [hidden email]] On Behalf Of Joseph J Alotta

> Sent: Friday, May 30, 2014 11:55 AM

> To: [hidden email]

> Subject: [Newbies] debugging over loops

>

> Greetings,

>

> How do I debug over loops?  I tried using the "over" step and the "through"

> step, but that just keeps me inside the loop.

>

> I don't know what the other buttons do, like "tally".  Is there somewhere

> that explains this?

>

> Sincerely,

>

> Joe.

>

>

>

> _______________________________________________

> Beginners mailing list

> [hidden email]

> http://lists.squeakfoundation.org/mailman/listinfo/beginners

 

_______________________________________________
Beginners mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/beginners