Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uwm.edu!rpi!dali.cs.montana.edu!uakari.primate.wisc.edu!sdd.hp.com!elroy.jpl.nasa.gov!hacgate!ashtate!dbase!cy
From: cy@dbase.A-T.COM (Cy Shuster)
Newsgroups: comp.sys.mac.programmer
Subject: Re: SADE/LIB-LINK An S&L Crisis??
Message-ID: <672@dbase.A-T.COM>
Date: 20 Aug 90 21:56:06 GMT
References: <23759@dartvax.Dartmouth.EDU> <2809@neptune.inf.ethz.ch>
Reply-To: cy@dbase.UUCP (Cy Shuster)
Organization: Ashton Tate Development Center Glendale, Calif.
Lines: 23

In article <23759@dartvax.Dartmouth.EDU> llama@eleazar.dartmouth.edu (Joe Francis) writes:
>I have been unable to set SADE breakpoints in Library source files
>despite the fact that the library was Lib'd with -sym full and the
>application was linked with -sym full.  I can break in app sources
>just fine.

I've also seen this behavior. Sometimes it helps to be explicit about
naming the breakpoints. See the SADE manual: there's a full qualification
scheme, like "break \myunit\myfunc.(12)". But the most reliable way for
me is to "open source myfile.c" (source says open read only), then
*point* to the line of code, and say "There! Break *right there*!"
(command-B also helps).

If only it would display globals, regardless of where they were defined...
and macros! Like Think C! If only we had fewer than 255 segments, I could
be using it...

--Cy--
cy@dbase.a-t.com

P.S. Anyone see that exciting new product "dBASE IV RunTime PLUS for
Macintosh, Version 1.1" at MacWorld? (The name spirals all the way 
around the T-shirt).