Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!wuarchive!uunet!seismo!dimacs.rutgers.edu!rutgers!cbmvax!darren
From: darren@cbmvax.commodore.com (Darren Greenwald)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: What the hell is SDB doing?
Message-ID: <21445@cbmvax.commodore.com>
Date: 9 May 91 16:06:01 GMT
References: <1991May8.160123.5313@zorch.SF-Bay.ORG> <52607@apple.Apple.COM>
Reply-To: darren@cbmvax.commodore.com (Darren Greenwald)
Organization: Commodore, West Chester, PA
Lines: 26

In article <52607@apple.Apple.COM> farrier@Apple.COM (Cary Farrier) writes:
>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.
>

No, I've noticed the same problem with SDB; it seems to want to single
step through linked lib calls.  It may be fixed in a more recent version;
I noticed it after I upgraded (the original SDB doesn't do this).  It may
be fixed now (I don't remember the revision numbers off hand).

Acts like its looking for source code out there when there isn't any.

>
>>Mike Smithwick - ames!zorch!mike
>
>-- Cary