Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!apple!farrier
From: farrier@Apple.COM (Cary Farrier)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: What the hell is SDB doing?
Message-ID: <52607@apple.Apple.COM>
Date: 8 May 91 23:08:33 GMT
References: <1991May8.160123.5313@zorch.SF-Bay.ORG>
Organization: My Amiga 500 and I
Lines: 26

In article <1991May8.160123.5313@zorch.SF-Bay.ORG> mike@zorch.SF-Bay.ORG (Mike Smithwick) writes:
>[]
>
>Ok, so I am stepping thru some code with SDB. I come to something like
>fopen(). The harddrive kicks in (flutter, flutter, flutter), indicating
>some sort of activity. And it may stay active for SEVERAL MINUTES! Doing
>a memset on 100bytes does the same thing along with most library functions.
>Using "t" (which supposedly steps "over" the function) doesn't help either.

Something is severely wrong with your system if memset and most of the
library functions cause your harddrive to kick in, unless they are 
dos library functions.

Using 't' always works fine for me, are you compiling/linking with the 
debugger options, and are your source code files unmodified since 
your last compile?  One thing that throws me for a spin is when I modify
a source file, then try to use SDB.  I usually catch on when I start
stepping through comments, though :-).

>"There is no problem to big that can't be solved with high explosives"-Rush

Of course, you've already suggested one solution.

>Mike Smithwick - ames!zorch!mike

-- Cary