scutil killed by launchd on exit

Got a problem with Viscosity or need help? Ask here!

ev


Post by ev » Thu Jan 15, 2009 8:04 pm
Hi,

After a hiatus I've recently started evaluating Viscosity; I noticed the following message in system.log on Viscosity's exit:
Code: Select all
Jan 15 09:53:10 bob com.apple.launchd[77] ([0x0-0x1c01c].com.viscosityvpn.Viscosity[749]): Stray process with PGID equal to this dead job: PID 757 PPID 1 scutil
Jan 15 09:53:11 bob ReportCrash[758]: Formulating crash report for process scutil[757]
The crash report reads:
Code: Select all
Process:         scutil [757]
Path:            /usr/sbin/scutil
Identifier:      scutil
Version:         ??? (???)
Code Type:       X86 (Native)
Parent Process:  launchd [1]

Date/Time:       2009-01-15 09:53:10.333 +0100
OS Version:      Mac OS X 10.5.6 (9G55)
Report Version:  6

Exception Type:  EXC_CRASH (SIGQUIT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Crashed Thread:  0

Thread 0 Crashed:
0   libSystem.B.dylib             	0x9005fbce read + 10
1   libSystem.B.dylib             	0x90097265 __srefill + 295
2   libSystem.B.dylib             	0x9009705e fgets + 108
3   scutil                        	0x0000207e getLine + 90
4   scutil                        	0x00002183 process_line + 33
5   scutil                        	0x00002a89 main + 1494
6   scutil                        	0x00001c7e start + 54

Thread 1:
0   libSystem.B.dylib             	0x9005f1c6 mach_msg_trap + 10
1   libSystem.B.dylib             	0x900669bc mach_msg + 72
2   com.apple.CoreFoundation      	0x90de40ae CFRunLoopRunSpecific + 1790
3   com.apple.CoreFoundation      	0x90de4d34 CFRunLoopRun + 84
4   scutil                        	0x00003e96 _watcher + 158
5   libSystem.B.dylib             	0x90090095 _pthread_start + 321
6   libSystem.B.dylib             	0x9008ff52 thread_start + 34

Thread 0 crashed with X86 Thread State (32-bit):
  eax: 0x00000004  ebx: 0x90097148  ecx: 0xbffff68c  edx: 0x9005fbce
  edi: 0x000000ff  esi: 0xa00105e0  ebp: 0xbffff6c8  esp: 0xbffff68c
   ss: 0x0000001f  efl: 0x00000287  eip: 0x9005fbce   cs: 0x00000007
   ds: 0x0000001f   es: 0x0000001f   fs: 0x00000000   gs: 0x00000037
  cr2: 0xb0081c58

Binary Images:
    0x1000 -    0x12fff +scutil ??? (???) <f6d4bd4e439fb213317225b20aaee9c4> /usr/sbin/scutil
   0x21000 -    0x37fea  libedit.2.dylib ??? (???) <c98b30cb0c9e4252892382daf57fa108> /usr/lib/libedit.2.dylib
0x8fe00000 - 0x8fe2db43  dyld 97.1 (???) <100d362e03410f181a34e04e94189ae5> /usr/lib/dyld
0x90003000 - 0x90032ff7  libncurses.5.4.dylib ??? (???) <00632d5180ac31e2cd437a1ce9d08562> /usr/lib/libncurses.5.4.dylib
0x9005e000 - 0x901c5ff3  libSystem.B.dylib ??? (???) <d68880dfb1f8becdbdac6928db1510fb> /usr/lib/libSystem.B.dylib
0x90d71000 - 0x90ea4fff  com.apple.CoreFoundation 6.5.5 (476.17) <4a70c8dbb582118e31412c53dc1f407f> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x92235000 - 0x92239fff  libmathCommon.A.dylib ??? (???) /usr/lib/system/libmathCommon.A.dylib
0x94e49000 - 0x94f29fff  libobjc.A.dylib ??? (???) <7b92613fdf804fd9a0a3733a0674c30b> /usr/lib/libobjc.A.dylib
0x952db000 - 0x952e2fe9  libgcc_s.1.dylib ??? (???) <28a7cbc3a5ca2982d124668306f422d9> /usr/lib/libgcc_s.1.dylib
0x96beb000 - 0x96c22fff  com.apple.SystemConfiguration 1.9.2 (1.9.2) <8b26ebf26a009a098484f1ed01ec499c> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
0x96cc9000 - 0x96e01ff7  libicucore.A.dylib ??? (???) <18098dcf431603fe47ee027a60006c85> /usr/lib/libicucore.A.dylib
0x96e5d000 - 0x96ebaffb  libstdc++.6.dylib ??? (???) <6106b1f2b0b303b06ae476253dbb5f3f> /usr/lib/libstdc++.6.dylib
0x96eed000 - 0x96f18fe7  libauto.dylib ??? (???) <2072d673706bbe463ed2426af57a28d7> /usr/lib/libauto.dylib
0xfffe8000 - 0xfffebfff  libobjc.A.dylib ??? (???) /usr/lib/libobjc.A.dylib
0xffff0000 - 0xffff1780  libSystem.B.dylib ??? (???) /usr/lib/libSystem.B.dylib
Viscosity seems to work flawlessly; the crash reports piling up are just a nuisance.

James

User avatar
Posts: 1876
Joined: Thu Sep 04, 2008 9:27 pm

Post by James » Fri Jan 16, 2009 12:03 am
Thanks for the report ev. It appears to occur if the ViscosityHelper application isn't terminated before Viscosity itself exits. I'll make sure that this doesn't occur in future versions.

Thanks
James
James Bekkema
Viscosity Developer

Web: http://www.sparklabs.com
Support: http://www.sparklabs.com/support
Twitter: http://twitter.com/sparklabs
2 posts Page 1 of 1