dorner@pequod.cso.uiuc.edu (Steve Dorner) (11/20/89)
Time for another stupid MPW(/SADE?) question.
Two segments are showing up (locked) in (the middle of) my heap;
they're named "SACONSOLE" and "SADEV". I've tried
poking through them looking for likely routine names, and then
UnloadSeg'ing them, to no avail (in fact, the only things in them
that look like routine names to me are the names of things that
must be in my main segment, since UnloadSeging them makes my application
very, very unhappy).
Anyway, any MPW 3.0/SADE users out there who can give give me some
fodder for UnloadSeg to get rid of these nasty segments?
(The bonus question is, of course, WHY they're there. They ain't mentioned
in (at least the index of) the MPW or SADE docs).
Thanks.
--
Steve Dorner, U of Illinois Computing Services Office
Internet: s-dorner@uiuc.edu UUCP: {convex,uunet}!uiucuxc!dorner
IfUMust: (217) 244-1765levin@bbn.com (Joel B Levin) (11/22/89)
In article <1989Nov19.225448.7891@ux1.cso.uiuc.edu> dorner@pequod.cso.uiuc.edu (Steve Dorner) writes: |Two segments are showing up (locked) in (the middle of) my heap; |they're named "SACONSOLE" and "SADEV". . . . | |Anyway, any MPW 3.0/SADE users out there who can give give me some |fodder for UnloadSeg to get rid of these nasty segments? (My knowledge is a bit limited, but the following is generally correct I think.) Stuff that's required for MPW tools (things that use "standard," i.e., non-Mac-Toolbox library routines normally found in Unix-like development systems) go into these segments. If they are present in an application, you have used some feature of these libraries rather than sticking strictly to the Toolbox. Despite the names, they have nothing to do with SADE. /JBL Nets: levin@bbn.com | or {...}!bbn!levin | POTS: (617)873-3463 |