Where should the type information be 347

Ah, that's the magic incantation...thanks :-). Can you create a programmable logic analyzer?

address).

This is a start. Now if you can do something with a bit mask and trapping.

We did in a rudimentary way. We had the push down list (I think you guys would call it a stack?). There many PDLs in one monitor crash. There the users', the exec mode, the user-mode exec. And then there were software hooks that would keep a trace but nobody would run that on a production system unless the bug couldn't be reproduced elsewhere.

I'd better commit a caveat in this is the way we did stuff with that old hardware. It would be a non-feature if all of those hooks have been removed in today's architectures.

Sure.

but.butt..butt.. Isn't there a way to tell where the orders for a write in a particular location came from?

in

Yes. That is to be expected when you run device drivers as a user mode program with no exec protections in place.

I have been getting the feeling that some people are talking about running in production rather than debugging. There is still a difference between these two activities...isn't there?

BAH

Subtract a hundred and four for e-mail.