ldo@waikato.ac.nz (Lawrence D'Oliveiro, Waikato University) (03/26/91)
I downloaded the release version of MacsBug 6.2 a few days ago, and installed it on my LC at home. One of the things I tried to do was set a breakpoint on one of the HFSDispatch calls--CatMove or GetCatInfo or something, I forget. Imagine my surprise when I got an error about the symbol HFSDispatch being undefined! Further checking revealed that trap $A060 is named as FSDispatch, not HFSDispatch, and yet all the macros for the calls on this trap use the name HFSDispatch! A workaround is to define HFSDispatch as a macro equating to FSDispatch (or $A060). You could add this as a permanent macro with ResEdit. I just checked MacsBug 6.1 (which I'm still running on my Mac II at work), and it names trap $A060 as HFSDispatch. So why the change? On a related note, is it possible to add new A-trap definitions to MacsBug? I realize only Apple is allowed to define new traps, but the fact remains that MacsBug always seems to be a few releases behind, or we hit a bug like the one above. For instance, MacsBug 6.2 knows about Gestalt ($A0AD), but not about SndDispatch ($A800). Lawrence D'Oliveiro fone: +64-71-562-889 Computer Services Dept fax: +64-71-384-066 University of Waikato electric mail: ldo@waikato.ac.nz Hamilton, New Zealand 37^ 47' 26" S, 175^ 19' 7" E, GMT+12:00 To someone with a hammer and a screwdriver, every problem looks like a nail with threads.