GST development and debugging

Hi Paolo,

I got to wondering how you are going to debug the sockets/SMTP fault
that I posted just now...

This comes in the context of me writing a larger script than normal and
I've been wondering for some time, what is best practice for GST
development.

Tools
I've been breaking a task into Classes and then write a test method or
two to exercise the class. Then I string them together on the command
line or when completed inside a file. Divide and Conquer!
I use
  - vi and Transcript output. The inspect and printNl methods in particular.
  - gst-blox is also useful though writing to an image other than the
default image doesn't seem to work which limits its usefulness as I like
to save multiple images in case of a crash and to be able to go back if
a solution isn't working.

What tools do you use, and in particular how would you go about
debugging sockets?

Also, a quick example of how to use Debug would be really appreciated.

I understand you're busy today, so a post next week is sweet as.

Stephen


_______________________________________________
help-smalltalk mailing list
[hidden email]
http://lists.gnu.org/mailman/listinfo/help-smalltalk

> What tools do you use, and in particular how would you go about
> debugging sockets?

I usually go with vi/printNl.  Scripting language debuggers are actually
a bit primitive (not just gst).

But well, in this case I suppose I'd start with gdb, because it looks
like a C crash (probably something wrong is being done by the socket
bindings).  From the backtrace I can see what is crashing, but it
requires gdb to understand what wild address it is looking at.

Paolo


_______________________________________________
help-smalltalk mailing list
[hidden email]
http://lists.gnu.org/mailman/listinfo/help-smalltalk