From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=BAYES_00,INVALID_DATE autolearn=no autolearn_force=no version=3.4.4 Path: utzoo!utgpu!watserv1!watmath!att!linac!uwm.edu!zaphod.mps.ohio-state.edu!usc!apple!agate!linus!linus!emery From: emery@linus.mitre.org (David Emery) Newsgroups: comp.lang.ada Subject: Re: Determining Rendezvous Availability Message-ID: Date: 29 Nov 90 14:27:07 GMT References: <7463@hub.ucsb.edu> Sender: usenet@linus.mitre.org Organization: The Mitre Corporation, Bedford, MA In-reply-to: aleph@lime.ucsb.edu's message of 28 Nov 90 22:27:09 GMT List-Id: >From: aleph@lime.ucsb.edu (Thomas McVittie) >I could use our VADS debugger and ask for a listing of tasks (lt). But >the programs which we are analyzing make extensive use of the CLOCK >function when scheduling events, so stopping and restarting the program >dramatically change the behavior of the program. I suspect you'll always have a problem trying to get the information you want without affecting the basic program. Ever hear of a guy named Heisenberg? Your best bet is to get the information from the runtime environment, which of course makes your code very non-portable. dave emery emery@aries.mitre.org