Does anyone here read "Crash Logs"

[Imagine]

I have a Kensington StudioMouse, and I tried installing their new MouseWorks 2.4b on a G5/Panther. I can't get the settings in the prefernces to work, as I keep getting "Unable to connect to service". I've installed, uninstalled, and re-installed God knows how many times. It'll work under "Root Log In", but it won't anywhere else.

Can someone explain this to me? I'd appreciate it much. Thanks.

This is the crash log:

Host: Macintosh-Computer.local
Date/Time: 2003-11-08 02:03:13 -0800
OS Version: 10.3 (Build 7B85)

Command: MouseWorks Background (/Library/PreferencePanes/MouseWorks.prefPane/Contents/Resources/Support/MouseWorks Background.app/Contents/MacOS/MouseWorks Background)
PID: 411
Thread: 0

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_INVALID_ADDRESS (0x0001) at 0x002fb724

Thread 0 Crashed:
#0 0x900016e8 in szone_free (szone_free + 1320)
#1 0x9019ad00 in __CFStringDeallocate (__CFStringDeallocate + 88)
#2 0x90190f20 in CFRelease (CFRelease + 488)
#3 0x901981f0 in CFDictionaryRemoveAllValues (CFDictionaryRemoveAllValues + 664)
#4 0x901a61f8 in __CFDictionaryDeallocate (__CFDictionaryDeallocate + 84)
#5 0x90190f20 in CFRelease (CFRelease + 488)
#6 0x000ebc10 in GetUserSessionInfo (FastUserSwitch.c:79)
#7 0x0000ae40 in setup_backgroundapp__Fv (setup_backgroundapp__Fv + 636)
#8 0x0000b06c in main (main + 20)
#9 0x00003408 in _start (_start + 460)
#10 0x00003238 in start (start + 48)

PPC Thread State:
srr0: 0x900016e8 srr1: 0x0200f030 vrsave: 0x00000000
cr: 0x44002404 xer: 0x00000000 lr: 0x900016b4 ctr: 0x9002a500
r0: 0x900016b4 r1: 0xbffff900 r2: 0xa00011ac r3: 0x00000000
r4: 0x00000000 r5: 0x00000001 r6: 0x80808080 r7: 0x00000002
r8: 0x6f720000 r9: 0x9010bd84 r10: 0x0000017c r11: 0xa00044a4
r12: 0x9002a500 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000020
r20: 0xa00011d0 r21: 0x00000003 r22: 0x00030bec r23: 0x00000001
r24: 0x0030bec0 r25: 0x01800000 r26: 0x00000000 r27: 0x0000000b
r28: 0x0030be10 r29: 0x002fb720 r30: 0x00000000 r31: 0x900011d0

 

[Darkshadow]

It's trying to free some memory that it doesn't have allocated. Report it to Kensington as a bug, and send them a copy of the crash report.

I dunno why it works when you're logged in as root, though. It should have the same problem either way. You might want to mention that in the bug report.

 

[Captain Code]

It might be trying to load something into the kernel's memory, which is why it would work as root but not as anything else.