• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
OTDebugStr et al interrupt-safe?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

OTDebugStr et al interrupt-safe?


  • Subject: OTDebugStr et al interrupt-safe?
  • From: "Thomas E. Knowlton, Jr." <email@hidden>
  • Date: Thu, 26 Feb 2004 07:20:57 -0700

The subject basically nutshells my question: the documentation surrounding OTDebugStr, OTAssert, OTBreak, etc. is sparse.
Also, TN 1104 defers to NWOT with regard to OT routines.
Can anyone tell whether these routines are interrupt safe?

While I'm at it, I wonder whether anyone can tell me whether DebugStr, Debugger are interrupt-safe? I've been using them as though they are for some time, only to recently fail to see them documented in TN 1104. Is that an oversight on Apple's part, or am I using them in error in my notifier? Of course, there is a well-documented performance penalty using DebugStr with MacsBug, but so far that has not been a problem; I only increase the verbosity in my notifier while trying to isolate a problem, not during general testing and development.

Thanks,
--
Tommy
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.


  • Prev by Date: Re: Keeping OT app responsive?
  • Next by Date: notifier not called after SetSynchronous()?
  • Previous by thread: Re: Keeping OT app responsive?
  • Next by thread: notifier not called after SetSynchronous()?
  • Index(es):
    • Date
    • Thread