home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.mac.programmer
- Path: sparky!uunet!cs.utexas.edu!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!destroyer!gumby!kzoo!k044477
- From: k044477@hobbes.kzoo.edu (Jamie R. McCarthy)
- Subject: Re: Testing memory validity
- Message-ID: <1992Nov20.133613.13461@hobbes.kzoo.edu>
- Organization: Kalamazoo College
- References: <1992Nov19.180353.3151@hobbes.kzoo.edu>
- Date: Fri, 20 Nov 1992 13:36:13 GMT
- Lines: 25
-
- k044477@hobbes.kzoo.edu (Jamie R. McCarthy) writes:
- >Can anyone spell out an algorithm to me for predicting whether the
- >access of a certain memory location will yield a bus error?
-
- I've gotten three responses to date: two "try installing your own bus
- error handler"s and one "let me know what responses you've gotten."
-
- Unfortunately, even if I trusted myself to do something as grungy as
- modifying 680x0 exception vectors ("what, you mean I won't be able to
- use a source-level debugger"), I won't get the desired effect. This
- code has to "reserve" a range of memory before it gets access to it.
- I was hoping to trap potential, not actual, errors by detecting invalid
- ranges of memory.
-
- For example, I know that 0x50FF8001 is always an invalid location. I
- expect that some locations will always be valid, some always invalid,
- and that some will depend on which Mac, which addressing mode, which
- slots have cards in them, and lots of other stuff that I'm no expert on.
- I'm looking for a list of such considerations.
-
- Any help will be appreciated (and will make this (soon to be
- freely-distributable) code that much better).
- --
- Jamie McCarthy Internet: k044477@kzoo.edu AppleLink: j.mccarthy
- I suppose ya don't think I was run over by a streetcar!
-