home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!usc!enterpoop.mit.edu!eru.mt.luth.se!lunic!sunic!kth.se!dront.nada.kth.se!d88-jwa
- From: d88-jwa@dront.nada.kth.se (Jon Wtte)
- Newsgroups: comp.sys.mac.programmer
- Subject: Re: I will kill or die for this tool
- Message-ID: <1992Dec21.102233.2646@kth.se>
- Date: 21 Dec 92 10:22:33 GMT
- References: <1992Dec21.043540.20183@hobbes.kzoo.edu>
- Sender: usenet@kth.se (Usenet)
- Organization: Royal Institute of Technology, Stockholm, Sweden
- Lines: 21
- Nntp-Posting-Host: dront.nada.kth.se
-
- In <1992Dec21.043540.20183@hobbes.kzoo.edu> k044477@hobbes.kzoo.edu (Jamie R. McCarthy) writes:
-
- >Does anything like this exist already? Can it be done with a macro
- >(break on these a-traps, check the state byte, continue iff the locked
- >bit is set)? Does anyone with lots of free time want to write it?
- >Or should I tack this onto my Things I'd Really Like To Write list?
-
- When you have problems like these; try patching HLock etc
- from within your application to check your handles. Patching
- within an application only affects that application, and the
- patches are really easy to debug, too, since you can use the
- source debugger.
-
- Cheers,
-
- / h+
-
- --
- -- Jon W{tte, h+@nada.kth.se, Mac Hacker Deluxe --
- This signature is kept shorter than 4 lines in the interests of UseNet
- S/N ratio.
-