Quite a regular
Joined: 2006/12/2 0:35 Last Login
: 1/19 10:37
From Sydney
Group:
Registered Users
|
@Chris
It says input.device but that is merely where the CPU was executing when the fault occurred. Since the stack trace shows Intuition below the input.device, it is likely that Intuition was attempting to carry out some processing for "a third party" when it hit a snag and crashed.
I don't know if you were running anything except the OS, but it could be some repetitive task like updating the title string on a window every few seconds, updating the Workbench screen title string, etc. It would seem that it ran into a problem with a null pointer (or to be exact, a pointer of "-1").
Of course, it could also be a problem with keyboard or mouse input that has been requested with bad parameters.
Where it came from is anybody's guess, but if you can eliminate "foreign" programs, you may be able to narrow it down.
|