Newsgroups: comp.lang.smalltalk
Path: cantaloupe.srv.cs.cmu.edu!das-news2.harvard.edu!fas-news.harvard.edu!newspump.wustl.edu!news.ecn.bgu.edu!psuvax1!news.pop.psu.edu!news.cac.psu.edu!howland.reston.ans.net!ix.netcom.com!netcomsv!netcomsv!slcgate!servio!servio!marcs
From: marcs@slc.com (Marc San Soucie)
Subject: Re: Smalltalks need less intrusive breakpoint mechanism
Message-ID: <marcs.795289127@servio>
Sender: news@slc.com (USENET News)
Nntp-Posting-Host: servio
Organization: Servio Corporation, Beaverton OR, USA
References: <ab7e0ab6040210046b0d@[192.55.204.253]> <2f5d0471.5a4f45@zoe.network23.com>
Date: 15 Mar 95 17:38:47 GMT
Lines: 24

terry@zoe.network23.com (Terry Raymond) writes:

> David Simmons  <quasar@QKS.COM> wrote:

> > The way STA works, you can set breakpoints on methods (or on operations in
> > or around methods) using an external facility that does not change the
> > source of the method in any way.  Thus freeing the author to forget about
> > their debug code once they are finished debugging [as opposed to having to
> > go back and remove breakpoints from the source code to each of the methods
> > they were debugging].

> Are the breakpoints on method entry or anywhere in the method?
> When is STA being ported to OS/2?

Breakpoints in GemStone's Smalltalk work the same way - have done so for
years. Breakpoints can be set on method entry or on any "step point" -
message send - in the method. Single-stepping into or over message sends is
supported as well. This kind of breakpoint requires building support into
the VM.

    Marc San Soucie
    Servio Corporation
    Beaverton, Oregon
    marcs@slc.com
