|
From: Bernard B. <be...@lp...> - 2007-01-05 21:40:00
|
>This is happening with my "in development" version where I have forced >DriverOpen() to return an error code. Clearly, more than just returning an >error will need to be done. >From memory, other procedures are called at startup before DriverOpen() is called. The "hanging" is likely to be caused by an interrupt that is launched before calling DriverOpen(). This could be traced via the debugger, but it is a lenghty process. I will have a quick look at the code to find more clues. >I discovered that it is not actually hanging, it just seems to ignore all >events for an extended period. Eventually, I can switch back to CodeWarrior >but the "pause" happens again when switching back to BP2 and I can never >actually do anything in BP2 (except switch out). Looks like a loop in an interrupt. >No need to rush or spend a lot of time coming up with a solution right now. >I looked at it some more this morning and I think that I will just leave the >issue for the moment. The Carbon version will eventually have to leave both >OMS and the built-in driver behind, but I can continue with many other >things before solving this issue. This is wise. Fiddling with the drivers might anyway generate other bugs that could be confused with problems caused by the porting. Bernard Bel |
