CallMeDave Posted January 7, 2003 Report Share Posted January 7, 2003 In reply to: The one thing my iMac DV and the iMac G4 have in common is that they both have French as the Mac OS interface language Oh man, yet _another_ bit of specific information left out of your previous twelve posts? Some mornings I just ought to stay in bed. Dave Link to comment Share on other sites More sharing options...
steffi Posted January 8, 2003 Report Share Posted January 8, 2003 Please note I'm getting this same error on my machine and my version if the US/English version. For me it will crash with fix_prebinding immediately when I change tabs from Immediate to Automate otherwise if I just wait 5 seconds the prebinding will also crash ********** Date/Time: 2003-01-08 11:32:27 +0000 OS Version: 10.2.3 (Build 6G30) Host: Steffi-Computer.local. Command: fix_prebinding PID: 762 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000054 Thread 0 Crashed: #0 0x000152a4 in 0x152a4 #1 0x0000c3d8 in 0xc3d8 #2 0x0000c0ec in 0xc0ec #3 0x0000b3ac in 0xb3ac #4 0x00007b20 in 0x7b20 #5 0x00004250 in 0x4250 #6 0x0000290c in 0x290c #7 0x00002414 in 0x2414 #8 0x00002a2c in 0x2a2c #9 0x90031c44 in mach_msg_server #10 0x00002c40 in 0x2c40 #11 0x00002f48 in 0x2f48 #12 0x00002188 in 0x2188 #13 0x00002008 in 0x2008 PPC Thread State: srr0: 0x000152a4 srr1: 0x0200d030 vrsave: 0x00000000 xer: 0x00000000 lr: 0x00015254 ctr: 0x90000f00 mq: 0x00000000 r0: 0x000017e8 r1: 0xbffff430 r2: 0x00000000 r3: 0x00173a78 r4: 0x00000003 r5: 0x00000001 r6: 0x00000040 r7: 0x00032230 r8: 0x00001680 r9: 0x00000014 r10: 0x00032230 r11: 0x0016d428 r12: 0x90000f00 r13: 0x000321b8 r14: 0x00032234 r15: 0x0000003f r16: 0x00001770 r17: 0x00001f80 r18: 0x00171c00 r19: 0x00000010 r20: 0x00032234 r21: 0x000321b8 r22: 0x00173630 r23: 0x00000030 r24: 0x00032230 r25: 0x03a9bc60 r26: 0x00032234 r27: 0x00173a48 r28: 0x00000033 r29: 0x00032230 r30: 0x00001680 r31: 0x00014914 Link to comment Share on other sites More sharing options...
bernarddesgagne Posted January 8, 2003 Author Report Share Posted January 8, 2003 At least, there are two of us now (three if we include my friend's iMac G4). Thank you for posting your message, Steffi. Dave, I was not trying to "hold back" information. The OS interface language just did not seem to be factor that mattered, even though I was starting to have doubts recently since neither you nor Dantz could reproduce the problem. As you can see now, it seems that my first feeling was right. You went through a lot of trouble to help me with this matter, Dave. Thank you very much. Now, let Dantz take their responsibility and do their homework properly. Because they have the source code and they have access to Apple's developer information regarding 10.2.3, they do not necessarily have to be able to reproduce the problem in order to fix it. And they have at least two users to do the testing if necessary. Link to comment Share on other sites More sharing options...
CallMeDave Posted January 8, 2003 Report Share Posted January 8, 2003 In reply to: Please note I'm getting this same error on my machine and my version if the US/English version. Steffi, what is your hardware setup? Dave Link to comment Share on other sites More sharing options...
CallMeDave Posted January 8, 2003 Report Share Posted January 8, 2003 In reply to: iMac DV 450 MHz with internal CD-ROM 768 MB RAM External LaCie Firewire 56 GB hard drive (where the Retrospect catalogs are stored) External LaCie Firewire CD-RW, model LTR-48125W Have you tried launching Retrospect without the external FW devices connected to the iMac? Dave Link to comment Share on other sites More sharing options...
CallMeDave Posted January 8, 2003 Report Share Posted January 8, 2003 Bingo. Taking my test iMac that exhibited no problem, I attached an external Maxtor FireWire drive and experienced fix_prebinding launch and then crash. Running the update_prebinding command showed no errors relating to Retrospect, however. Disconnecting the FW drive (and restarting) had no palative effect; it looks as if this machine will continue to experience the problem (until I wipe the drive). The console logs are probably not helpful to Dantz, since they do not contain debug code. But this appears to be the missing link to reproduce. Dave Link to comment Share on other sites More sharing options...
bernarddesgagne Posted January 8, 2003 Author Report Share Posted January 8, 2003 Regarding these devices: - External LaCie Firewire 56 GB hard drive (where the Retrospect catalogs are stored) - External LaCie Firewire CD-RW, model LTR-48125W Yes, I have tried with and without the external devices. It does not make a difference. The crash happens the same way. Besides. The iMac G4 does not have any external devices, and the crash occurs anyway. Link to comment Share on other sites More sharing options...
CallMeDave Posted January 8, 2003 Report Share Posted January 8, 2003 After connecting the external FW drive, my test iMac crashed the fix_prebinding each time Retrospect was launched. After deleting the file: /Library/Caches/com.apple.LaunchServices.LocalCache.csstore the crashes went away. I tried in vain to again bring forth the crash, disconnecting the FW drives, restarting with them connected and disconnected, etc, but as of now Retrospect again works without causing any processes to crash. In the case of your test G4, perhpas an external FW drive _had_ lived on that machine in the past? Dave Link to comment Share on other sites More sharing options...
robballan Posted January 8, 2003 Report Share Posted January 8, 2003 Forgive me for interrupting, but in fact Retrospect is not the only application to trigger fix_prebinding crashes. I began having a number of them triggered by a variety of application launches with the recent 10.2.3 software update. The fix in general is relatively simple: launch Terminal, type "sudo update_prebinding -root /" and then your admin password, and let it run. However, this does not fix an existing installation of Retrospect. Reinstalling also does not work. Link to comment Share on other sites More sharing options...
bernarddesgagne Posted January 9, 2003 Author Report Share Posted January 9, 2003 As you say, Rob, running update_prebinding does not fix Retrospect. Reinstalling Retrospect does not work neither, nor reinstalling your whole system, nor unplugging devices. In Apple's forums, I noticed that users were having fix_prebinding crashes caused by other applications than Retrospect. OmniWeb seems to be one of them, for example. However, not all applications cause these crashes. Far from that. And certainly not all applications still cause the crash after you update the prebinding information for your whole system. As I mentionned previously, on my computer, Retrospect is the only application that causes the fix_prebiding crash. Also, these crashes seem to be linked to Mac OS 10.2.3, and not to previous versions of the OS. Therefore, my hypothesis right now is that the crashes are caused by an incompatibility between some applications and Mac OS 10.2.3. When you try to run update_prebinding on the whole hard drive, Retrospect does no cause any error. But if you try to specifically update the prebinding of the files in the Retrospect 5 folder, you get all kinds of errors. Here is a sample: sudo update_prebinding -root "/Applications/Retrospect 5.0" 2003-01-08 21:14:08.789 update_prebinding[553] Start of update_prebinding 2003-01-08 21:14:08.797 update_prebinding[553] Start of search for binaries in packages... 2003-01-08 21:14:08.799 update_prebinding[553] Discover library dependencies (0/1 complete) 2003-01-08 21:14:08.815 update_prebinding[553] Discover library dependencies (1/1 complete) 2003-01-08 21:14:08.817 update_prebinding[553] Build dependency graph (0/1 complete) 2003-01-08 21:14:08.819 update_prebinding[553] Start of search for binaries on disk... 2003-01-08 21:14:09.100 update_prebinding[553] update_prebinding (finding dependent libraries for /Applications/Retrospect 5.0/System/Library/Frameworks/Carbon.framework/Versions/A/Carbon): can't open file: /Applications/Retrospect 5.0/System/Library/Frameworks/Carbon.framework/Versions/A/Carbon (No such file or directory) 2003-01-08 21:14:09.104 update_prebinding[553] update_prebinding (finding dependent libraries for /Applications/Retrospect 5.0/System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa): can't open file: /Applications/Retrospect 5.0/System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa (No such file or directory) [...] The binding paths above are erroneous. Isn't this a clear hint about where the problem comes from? To update the prebinding, Mac OS needs to get some information from the application as to what system library objects it needs to use. In this case, it seems that Mac OS 10.2.3 is not getting the information properly from Retrospect (and likely from other applications which are not quite ready for 10.2.3). Again, I can never say it enough: this is an issue that only Dantz's programmers can solve. They are the ones who can find out what needs to be changed in the code for the prebinding to occur properly. I suggest they contact OmniWeb's programmers, who have already recognized that the fix_prebinding crash is an issue. They are presently trying to find out how to fix it. We are wasting our time discussing and doing Dantz's job. Link to comment Share on other sites More sharing options...
bernarddesgagne Posted January 9, 2003 Author Report Share Posted January 9, 2003 Dave, I unplugged my Firewire devices, then I deleted /Library/Caches/com.apple.LaunchServices.LocalCache.csstore. It does not make a difference. Retrospect still makes fix_prebinding crash. Link to comment Share on other sites More sharing options...
CallMeDave Posted January 9, 2003 Report Share Posted January 9, 2003 In reply to: The binding paths above are erroneous. Isn't this a clear hint about where the problem comes from? To update the prebinding, Mac OS needs to get some information from the application as to what system library objects it needs to use. In this case, it seems that Mac OS 10.2.3 is not getting the information properly from Retrospect (and likely from other applications which are not quite ready for 10.2.3). It's more likely that specifying the -root flag for update_prebinding this way is an incorrect use of the tool. Here's what happens when I do the same thing with Safari, certainly a 10.2.3 savvy application: root# update_prebinding -root /Applications/Safari.app/ 2003-01-08 20:32:54.900 update_prebinding[2737] Start of update_prebinding 2003-01-08 20:32:54.911 update_prebinding[2737] Start of search for binaries in packages... 2003-01-08 20:32:54.913 update_prebinding[2737] Discover library dependencies (0/1 complete) 2003-01-08 20:32:54.927 update_prebinding[2737] Discover library dependencies (1/1 complete) 2003-01-08 20:32:54.929 update_prebinding[2737] Build dependency graph (0/1 complete) 2003-01-08 20:32:54.931 update_prebinding[2737] Start of search for binaries on disk... 2003-01-08 20:32:55.114 update_prebinding[2737] update_prebinding (finding dependent libraries for /Applications/Safari.app/System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa): can't open file: /Applications/Safari.app/System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa (No such file or directory) 2003-01-08 20:32:55.116 update_prebinding[2737] update_prebinding (finding dependent libraries for /Applications/Safari.app/usr/lib/libSystem.B.dylib): can't open file: /Applications/Safari.app/usr/lib/libSystem.B.dylib (No such file or directory) 2003-01-08 20:32:55.244 update_prebinding[2737] update_prebinding (finding dependent libraries for /Applications/Safari.app/System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices): can't open file: /Applications/Safari.app/System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices (No such file or directory) {etc} >We are wasting our time discussing and doing Dantz's job. And just yesterday you were offering to help test... Dave Link to comment Share on other sites More sharing options...
hughmcmillan Posted January 13, 2003 Report Share Posted January 13, 2003 I would just like Dantz and other forum readers, Bernard !, to know that I have also experienced the fix_prebinding crash log bug in Retrospect Workgroup 5.0.540 (English). I am on a G4 Quicksilver 867MHz with 768 MB running 10.2.3. I can't believe that there are not more people reporting this problem. It was experiencing this problem which caused me to join this forum. I have read every post in this thread and have tried most of the "solutions" with no success. Hopefully Dantz will fix this problem but I am not holding my breath. The good aspect of this seems to be that it does not affect the actual running of Retrospect Workgroup. -Hugh ********** Date/Time: 2002-12-30 19:24:59 -0500 OS Version: 10.2.3 (Build 6G30) Host: G4.local. Command: fix_prebinding PID: 6599 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x000001c1 Thread 0 Crashed: #0 0x000152a4 in 0x152a4 #1 0x0000c3d8 in 0xc3d8 #2 0x0000c0ec in 0xc0ec #3 0x0000b3ac in 0xb3ac #4 0x00007b20 in 0x7b20 #5 0x00004250 in 0x4250 #6 0x0000290c in 0x290c #7 0x00002414 in 0x2414 #8 0x00002a2c in 0x2a2c #9 0x90031c44 in mach_msg_server #10 0x00002c40 in 0x2c40 #11 0x00002f48 in 0x2f48 #12 0x00002188 in 0x2188 #13 0x00002008 in 0x2008 PPC Thread State: srr0: 0x000152a4 srr1: 0x0200d030 vrsave: 0x00000000 xer: 0x00000000 lr: 0x00015254 ctr: 0x90000f00 mq: 0x00000000 r0: 0x00001338 r1: 0xbffff430 r2: 0x00000000 r3: 0x04557cfc r4: 0x00000003 r5: 0x00000001 r6: 0x000001c0 r7: 0x00032230 r8: 0x00001248 r9: 0x00000001 r10: 0x00032230 r11: 0x00169eb8 r12: 0x90000f00 r13: 0x000321b8 r14: 0x00032234 r15: 0x00000036 r16: 0x000012c0 r17: 0x00001ea4 r18: 0x04555ef0 r19: 0x00000070 r20: 0x00032234 r21: 0x000321b8 r22: 0x04557984 r23: 0x00000027 r24: 0x00032230 r25: 0x02186c30 r26: 0x00032234 r27: 0x04557ccc r28: 0x00000029 r29: 0x00032230 r30: 0x00001248 r31: 0x00014914 ********** Date/Time: 2002-12-31 06:45:13 -0500 OS Version: 10.2.3 (Build 6G30) Host: G4.local. Command: fix_prebinding PID: 8331 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x000001c1 Thread 0 Crashed: #0 0x000152a4 in 0x152a4 #1 0x0000c3d8 in 0xc3d8 #2 0x0000c0ec in 0xc0ec #3 0x0000b3ac in 0xb3ac #4 0x00007b20 in 0x7b20 #5 0x00004250 in 0x4250 #6 0x0000290c in 0x290c #7 0x00002414 in 0x2414 #8 0x00002a2c in 0x2a2c #9 0x90031c44 in mach_msg_server #10 0x00002c40 in 0x2c40 #11 0x00002f48 in 0x2f48 #12 0x00002188 in 0x2188 #13 0x00002008 in 0x2008 PPC Thread State: srr0: 0x000152a4 srr1: 0x0200d030 vrsave: 0x00000000 xer: 0x00000000 lr: 0x00015254 ctr: 0x90000f00 mq: 0x00000000 r0: 0x00001338 r1: 0xbffff430 r2: 0x00000000 r3: 0x04557cfc r4: 0x00000003 r5: 0x00000001 r6: 0x000001c0 r7: 0x00032230 r8: 0x00001248 r9: 0x00000001 r10: 0x00032230 r11: 0x00169eb8 r12: 0x90000f00 r13: 0x000321b8 r14: 0x00032234 r15: 0x00000036 r16: 0x000012c0 r17: 0x00001ea4 r18: 0x04555ef0 r19: 0x00000070 r20: 0x00032234 r21: 0x000321b8 r22: 0x04557984 r23: 0x00000027 r24: 0x00032230 r25: 0x02186c30 r26: 0x00032234 r27: 0x04557ccc r28: 0x00000029 r29: 0x00032230 r30: 0x00001248 r31: 0x00014914 ********** Date/Time: 2002-12-31 06:52:46 -0500 OS Version: 10.2.3 (Build 6G30) Host: G4.local. Command: fix_prebinding PID: 9973 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x000001c1 Thread 0 Crashed: #0 0x000152a4 in 0x152a4 #1 0x0000c3d8 in 0xc3d8 #2 0x0000c0ec in 0xc0ec #3 0x0000b3ac in 0xb3ac #4 0x00007b20 in 0x7b20 #5 0x00004250 in 0x4250 #6 0x0000290c in 0x290c #7 0x00002414 in 0x2414 #8 0x00002a2c in 0x2a2c #9 0x90031c44 in mach_msg_server #10 0x00002c40 in 0x2c40 #11 0x00002f48 in 0x2f48 #12 0x00002188 in 0x2188 #13 0x00002008 in 0x2008 PPC Thread State: srr0: 0x000152a4 srr1: 0x0200d030 vrsave: 0x00000000 xer: 0x00000000 lr: 0x00015254 ctr: 0x90000f00 mq: 0x00000000 r0: 0x00001338 r1: 0xbffff430 r2: 0x00000000 r3: 0x04557cfc r4: 0x00000003 r5: 0x00000001 r6: 0x000001c0 r7: 0x00032230 r8: 0x00001248 r9: 0x00000001 r10: 0x00032230 r11: 0x00169eb8 r12: 0x90000f00 r13: 0x000321b8 r14: 0x00032234 r15: 0x00000036 r16: 0x000012c0 r17: 0x00001ea4 r18: 0x04555ef0 r19: 0x00000070 r20: 0x00032234 r21: 0x000321b8 r22: 0x04557984 r23: 0x00000027 r24: 0x00032230 r25: 0x02186c30 r26: 0x00032234 r27: 0x04557ccc r28: 0x00000029 r29: 0x00032230 r30: 0x00001248 r31: 0x00014914 ********** Date/Time: 2003-01-01 12:17:28 -0500 OS Version: 10.2.3 (Build 6G30) Host: G4.local. Command: fix_prebinding PID: 4786 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x000001c1 Thread 0 Crashed: #0 0x000152a4 in 0x152a4 #1 0x0000c3d8 in 0xc3d8 #2 0x0000c0ec in 0xc0ec #3 0x0000b3ac in 0xb3ac #4 0x00007b20 in 0x7b20 #5 0x00004250 in 0x4250 #6 0x0000290c in 0x290c #7 0x00002414 in 0x2414 #8 0x00002a2c in 0x2a2c #9 0x90031c44 in mach_msg_server #10 0x00002c40 in 0x2c40 #11 0x00002f48 in 0x2f48 #12 0x00002188 in 0x2188 #13 0x00002008 in 0x2008 PPC Thread State: srr0: 0x000152a4 srr1: 0x0200d030 vrsave: 0x00000000 xer: 0x00000000 lr: 0x00015254 ctr: 0x90000f00 mq: 0x00000000 r0: 0x00001338 r1: 0xbffff430 r2: 0x00000000 r3: 0x04557cfc r4: 0x00000003 r5: 0x00000001 r6: 0x000001c0 r7: 0x00032230 r8: 0x00001248 r9: 0x00000001 r10: 0x00032230 r11: 0x00169eb8 r12: 0x90000f00 r13: 0x000321b8 r14: 0x00032234 r15: 0x00000036 r16: 0x000012c0 r17: 0x00001ea4 r18: 0x04555ef0 r19: 0x00000070 r20: 0x00032234 r21: 0x000321b8 r22: 0x04557984 r23: 0x00000027 r24: 0x00032230 r25: 0x02186c30 r26: 0x00032234 r27: 0x04557ccc r28: 0x00000029 r29: 0x00032230 r30: 0x00001248 r31: 0x00014914 ********** Date/Time: 2003-01-11 20:33:45 -0500 OS Version: 10.2.3 (Build 6G30) Host: G4.local. Command: fix_prebinding PID: 519 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000054 Thread 0 Crashed: #0 0x000152a4 in 0x152a4 #1 0x0000c3d8 in 0xc3d8 #2 0x0000c0ec in 0xc0ec #3 0x0000b3ac in 0xb3ac #4 0x00007b20 in 0x7b20 #5 0x00004250 in 0x4250 #6 0x0000290c in 0x290c #7 0x00002414 in 0x2414 #8 0x00002a2c in 0x2a2c #9 0x90031c44 in mach_msg_server #10 0x00002c40 in 0x2c40 #11 0x00002f48 in 0x2f48 #12 0x00002188 in 0x2188 #13 0x00002008 in 0x2008 PPC Thread State: srr0: 0x000152a4 srr1: 0x0200d030 vrsave: 0x00000000 xer: 0x00000000 lr: 0x00015254 ctr: 0x90000f00 mq: 0x00000000 r0: 0x000017e8 r1: 0xbffff430 r2: 0x00000000 r3: 0x00173a78 r4: 0x00000003 r5: 0x00000001 r6: 0x00000040 r7: 0x00032230 r8: 0x00001680 r9: 0x00000014 r10: 0x00032230 r11: 0x0016d428 r12: 0x90000f00 r13: 0x000321b8 r14: 0x00032234 r15: 0x0000003f r16: 0x00001770 r17: 0x00001f80 r18: 0x00171c00 r19: 0x00000010 r20: 0x00032234 r21: 0x000321b8 r22: 0x00173630 r23: 0x00000030 r24: 0x00032230 r25: 0x03df4c60 r26: 0x00032234 r27: 0x00173a48 r28: 0x00000033 r29: 0x00032230 r30: 0x00001680 r31: 0x00014914 ********** Date/Time: 2003-01-11 20:34:02 -0500 OS Version: 10.2.3 (Build 6G30) Host: G4.local. Command: fix_prebinding PID: 533 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000054 Thread 0 Crashed: #0 0x000152a4 in 0x152a4 #1 0x0000c3d8 in 0xc3d8 #2 0x0000c0ec in 0xc0ec #3 0x0000b3ac in 0xb3ac #4 0x00007b20 in 0x7b20 #5 0x00004250 in 0x4250 #6 0x0000290c in 0x290c #7 0x00002414 in 0x2414 #8 0x00002a2c in 0x2a2c #9 0x90031c44 in mach_msg_server #10 0x00002c40 in 0x2c40 #11 0x00002f48 in 0x2f48 #12 0x00002188 in 0x2188 #13 0x00002008 in 0x2008 PPC Thread State: srr0: 0x000152a4 srr1: 0x0200d030 vrsave: 0x00000000 xer: 0x00000000 lr: 0x00015254 ctr: 0x90000f00 mq: 0x00000000 r0: 0x000017e8 r1: 0xbffff430 r2: 0x00000000 r3: 0x00172a78 r4: 0x00000003 r5: 0x00000001 r6: 0x00000040 r7: 0x00032230 r8: 0x00001680 r9: 0x00000014 r10: 0x00032230 r11: 0x0016c428 r12: 0x90000f00 r13: 0x000321b8 r14: 0x00032234 r15: 0x0000003f r16: 0x00001770 r17: 0x00001f80 r18: 0x00170c00 r19: 0x00000010 r20: 0x00032234 r21: 0x000321b8 r22: 0x00172630 r23: 0x00000030 r24: 0x00032230 r25: 0x01857c60 r26: 0x00032234 r27: 0x00172a48 r28: 0x00000033 r29: 0x00032230 r30: 0x00001680 r31: 0x00014914 ********** Date/Time: 2003-01-12 10:01:55 -0500 OS Version: 10.2.3 (Build 6G30) Host: G4.local. Command: fix_prebinding PID: 6029 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000054 Thread 0 Crashed: #0 0x000152a4 in 0x152a4 #1 0x0000c3d8 in 0xc3d8 #2 0x0000c0ec in 0xc0ec #3 0x0000b3ac in 0xb3ac #4 0x00007b20 in 0x7b20 #5 0x00004250 in 0x4250 #6 0x0000290c in 0x290c #7 0x00002414 in 0x2414 #8 0x00002a2c in 0x2a2c #9 0x90031c44 in mach_msg_server #10 0x00002c40 in 0x2c40 #11 0x00002f48 in 0x2f48 #12 0x00002188 in 0x2188 #13 0x00002008 in 0x2008 PPC Thread State: srr0: 0x000152a4 srr1: 0x0200d030 vrsave: 0x00000000 xer: 0x00000000 lr: 0x00015254 ctr: 0x90000f00 mq: 0x00000000 r0: 0x000017e8 r1: 0xbffff430 r2: 0x00000000 r3: 0x00173a78 r4: 0x00000003 r5: 0x00000001 r6: 0x00000040 r7: 0x00032230 r8: 0x00001680 r9: 0x00000014 r10: 0x00032230 r11: 0x0016d428 r12: 0x90000f00 r13: 0x000321b8 r14: 0x00032234 r15: 0x0000003f r16: 0x00001770 r17: 0x00001f80 r18: 0x00171c00 r19: 0x00000010 r20: 0x00032234 r21: 0x000321b8 r22: 0x00173630 r23: 0x00000030 r24: 0x00032230 r25: 0x01858c60 r26: 0x00032234 r27: 0x00173a48 r28: 0x00000033 r29: 0x00032230 r30: 0x00001680 r31: 0x00014914 ********** Date/Time: 2003-01-12 10:02:16 -0500 OS Version: 10.2.3 (Build 6G30) Host: G4.local. Command: fix_prebinding PID: 6042 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000054 Thread 0 Crashed: #0 0x000152a4 in 0x152a4 #1 0x0000c3d8 in 0xc3d8 #2 0x0000c0ec in 0xc0ec #3 0x0000b3ac in 0xb3ac #4 0x00007b20 in 0x7b20 #5 0x00004250 in 0x4250 #6 0x0000290c in 0x290c #7 0x00002414 in 0x2414 #8 0x00002a2c in 0x2a2c #9 0x90031c44 in mach_msg_server #10 0x00002c40 in 0x2c40 #11 0x00002f48 in 0x2f48 #12 0x00002188 in 0x2188 #13 0x00002008 in 0x2008 PPC Thread State: srr0: 0x000152a4 srr1: 0x0200d030 vrsave: 0x00000000 xer: 0x00000000 lr: 0x00015254 ctr: 0x90000f00 mq: 0x00000000 r0: 0x000017e8 r1: 0xbffff430 r2: 0x00000000 r3: 0x00172a78 r4: 0x00000003 r5: 0x00000001 r6: 0x00000040 r7: 0x00032230 r8: 0x00001680 r9: 0x00000014 r10: 0x00032230 r11: 0x0016c428 r12: 0x90000f00 r13: 0x000321b8 r14: 0x00032234 r15: 0x0000003f r16: 0x00001770 r17: 0x00001f80 r18: 0x00170c00 r19: 0x00000010 r20: 0x00032234 r21: 0x000321b8 r22: 0x00172630 r23: 0x00000030 r24: 0x00032230 r25: 0x01857c60 r26: 0x00032234 r27: 0x00172a48 r28: 0x00000033 r29: 0x00032230 r30: 0x00001680 r31: 0x00014914 ********** Date/Time: 2003-01-12 12:14:43 -0500 OS Version: 10.2.3 (Build 6G30) Host: G4.local. Command: fix_prebinding PID: 6202 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000054 Thread 0 Crashed: #0 0x000152a4 in 0x152a4 #1 0x0000c3d8 in 0xc3d8 #2 0x0000c0ec in 0xc0ec #3 0x0000b3ac in 0xb3ac #4 0x00007b20 in 0x7b20 #5 0x00004250 in 0x4250 #6 0x0000290c in 0x290c #7 0x00002414 in 0x2414 #8 0x00002a2c in 0x2a2c #9 0x90031c44 in mach_msg_server #10 0x00002c40 in 0x2c40 #11 0x00002f48 in 0x2f48 #12 0x00002188 in 0x2188 #13 0x00002008 in 0x2008 PPC Thread State: srr0: 0x000152a4 srr1: 0x0200d030 vrsave: 0x00000000 xer: 0x00000000 lr: 0x00015254 ctr: 0x90000f00 mq: 0x00000000 r0: 0x000017e8 r1: 0xbffff430 r2: 0x00000000 r3: 0x00173a78 r4: 0x00000003 r5: 0x00000001 r6: 0x00000040 r7: 0x00032230 r8: 0x00001680 r9: 0x00000014 r10: 0x00032230 r11: 0x0016d428 r12: 0x90000f00 r13: 0x000321b8 r14: 0x00032234 r15: 0x0000003f r16: 0x00001770 r17: 0x00001f80 r18: 0x00171c00 r19: 0x00000010 r20: 0x00032234 r21: 0x000321b8 r22: 0x00173630 r23: 0x00000030 r24: 0x00032230 r25: 0x01858c60 r26: 0x00032234 r27: 0x00173a48 r28: 0x00000033 r29: 0x00032230 r30: 0x00001680 r31: 0x00014914 ********** Date/Time: 2003-01-12 12:15:02 -0500 OS Version: 10.2.3 (Build 6G30) Host: G4.local. Command: fix_prebinding PID: 6215 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000054 Thread 0 Crashed: #0 0x000152a4 in 0x152a4 #1 0x0000c3d8 in 0xc3d8 #2 0x0000c0ec in 0xc0ec #3 0x0000b3ac in 0xb3ac #4 0x00007b20 in 0x7b20 #5 0x00004250 in 0x4250 #6 0x0000290c in 0x290c #7 0x00002414 in 0x2414 #8 0x00002a2c in 0x2a2c #9 0x90031c44 in mach_msg_server #10 0x00002c40 in 0x2c40 #11 0x00002f48 in 0x2f48 #12 0x00002188 in 0x2188 #13 0x00002008 in 0x2008 PPC Thread State: srr0: 0x000152a4 srr1: 0x0200d030 vrsave: 0x00000000 xer: 0x00000000 lr: 0x00015254 ctr: 0x90000f00 mq: 0x00000000 r0: 0x000017e8 r1: 0xbffff430 r2: 0x00000000 r3: 0x00172a78 r4: 0x00000003 r5: 0x00000001 r6: 0x00000040 r7: 0x00032230 r8: 0x00001680 r9: 0x00000014 r10: 0x00032230 r11: 0x0016c428 r12: 0x90000f00 r13: 0x000321b8 r14: 0x00032234 r15: 0x0000003f r16: 0x00001770 r17: 0x00001f80 r18: 0x00170c00 r19: 0x00000010 r20: 0x00032234 r21: 0x000321b8 r22: 0x00172630 r23: 0x00000030 r24: 0x00032230 r25: 0x01857c60 r26: 0x00032234 r27: 0x00172a48 r28: 0x00000033 r29: 0x00032230 r30: 0x00001680 r31: 0x00014914 ********** Date/Time: 2003-01-13 07:14:13 -0500 OS Version: 10.2.3 (Build 6G30) Host: G4.local. Command: fix_prebinding PID: 12201 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000054 Thread 0 Crashed: #0 0x000152a4 in 0x152a4 #1 0x0000c3d8 in 0xc3d8 #2 0x0000c0ec in 0xc0ec #3 0x0000b3ac in 0xb3ac #4 0x00007b20 in 0x7b20 #5 0x00004250 in 0x4250 #6 0x0000290c in 0x290c #7 0x00002414 in 0x2414 #8 0x00002a2c in 0x2a2c #9 0x90031c44 in mach_msg_server #10 0x00002c40 in 0x2c40 #11 0x00002f48 in 0x2f48 #12 0x00002188 in 0x2188 #13 0x00002008 in 0x2008 PPC Thread State: srr0: 0x000152a4 srr1: 0x0200d030 vrsave: 0x00000000 xer: 0x00000000 lr: 0x00015254 ctr: 0x90000f00 mq: 0x00000000 r0: 0x000017e8 r1: 0xbffff430 r2: 0x00000000 r3: 0x00173a78 r4: 0x00000003 r5: 0x00000001 r6: 0x00000040 r7: 0x00032230 r8: 0x00001680 r9: 0x00000014 r10: 0x00032230 r11: 0x0016d428 r12: 0x90000f00 r13: 0x000321b8 r14: 0x00032234 r15: 0x0000003f r16: 0x00001770 r17: 0x00001f80 r18: 0x00171c00 r19: 0x00000010 r20: 0x00032234 r21: 0x000321b8 r22: 0x00173630 r23: 0x00000030 r24: 0x00032230 r25: 0x01858c60 r26: 0x00032234 r27: 0x00173a48 r28: 0x00000033 r29: 0x00032230 r30: 0x00001680 r31: 0x00014914 ********** Date/Time: 2003-01-13 07:14:48 -0500 OS Version: 10.2.3 (Build 6G30) Host: G4.local. Command: fix_prebinding PID: 12214 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000054 Thread 0 Crashed: #0 0x000152a4 in 0x152a4 #1 0x0000c3d8 in 0xc3d8 #2 0x0000c0ec in 0xc0ec #3 0x0000b3ac in 0xb3ac #4 0x00007b20 in 0x7b20 #5 0x00004250 in 0x4250 #6 0x0000290c in 0x290c #7 0x00002414 in 0x2414 #8 0x00002a2c in 0x2a2c #9 0x90031c44 in mach_msg_server #10 0x00002c40 in 0x2c40 #11 0x00002f48 in 0x2f48 #12 0x00002188 in 0x2188 #13 0x00002008 in 0x2008 PPC Thread State: srr0: 0x000152a4 srr1: 0x0200d030 vrsave: 0x00000000 xer: 0x00000000 lr: 0x00015254 ctr: 0x90000f00 mq: 0x00000000 r0: 0x000017e8 r1: 0xbffff430 r2: 0x00000000 r3: 0x00172a78 r4: 0x00000003 r5: 0x00000001 r6: 0x00000040 r7: 0x00032230 r8: 0x00001680 r9: 0x00000014 r10: 0x00032230 r11: 0x0016c428 r12: 0x90000f00 r13: 0x000321b8 r14: 0x00032234 r15: 0x0000003f r16: 0x00001770 r17: 0x00001f80 r18: 0x00170c00 r19: 0x00000010 r20: 0x00032234 r21: 0x000321b8 r22: 0x00172630 r23: 0x00000030 r24: 0x00032230 r25: 0x01857c60 r26: 0x00032234 r27: 0x00172a48 r28: 0x00000033 r29: 0x00032230 r30: 0x00001680 r31: 0x00014914 ********** Date/Time: 2003-01-13 09:03:35 -0500 OS Version: 10.2.3 (Build 6G30) Host: G4.local. Command: fix_prebinding PID: 12259 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000054 Thread 0 Crashed: #0 0x000152a4 in 0x152a4 #1 0x0000c3d8 in 0xc3d8 #2 0x0000c0ec in 0xc0ec #3 0x0000b3ac in 0xb3ac #4 0x00007b20 in 0x7b20 #5 0x00004250 in 0x4250 #6 0x0000290c in 0x290c #7 0x00002414 in 0x2414 #8 0x00002a2c in 0x2a2c #9 0x90031c44 in mach_msg_server #10 0x00002c40 in 0x2c40 #11 0x00002f48 in 0x2f48 #12 0x00002188 in 0x2188 #13 0x00002008 in 0x2008 PPC Thread State: srr0: 0x000152a4 srr1: 0x0200d030 vrsave: 0x00000000 xer: 0x00000000 lr: 0x00015254 ctr: 0x90000f00 mq: 0x00000000 r0: 0x000017e8 r1: 0xbffff430 r2: 0x00000000 r3: 0x00173a78 r4: 0x00000003 r5: 0x00000001 r6: 0x00000040 r7: 0x00032230 r8: 0x00001680 r9: 0x00000014 r10: 0x00032230 r11: 0x0016d428 r12: 0x90000f00 r13: 0x000321b8 r14: 0x00032234 r15: 0x0000003f r16: 0x00001770 r17: 0x00001f80 r18: 0x00171c00 r19: 0x00000010 r20: 0x00032234 r21: 0x000321b8 r22: 0x00173630 r23: 0x00000030 r24: 0x00032230 r25: 0x01858c60 r26: 0x00032234 r27: 0x00173a48 r28: 0x00000033 r29: 0x00032230 r30: 0x00001680 r31: 0x00014914 ********** Date/Time: 2003-01-13 09:04:13 -0500 OS Version: 10.2.3 (Build 6G30) Host: G4.local. Command: fix_prebinding PID: 12271 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000054 Thread 0 Crashed: #0 0x000152a4 in 0x152a4 #1 0x0000c3d8 in 0xc3d8 #2 0x0000c0ec in 0xc0ec #3 0x0000b3ac in 0xb3ac #4 0x00007b20 in 0x7b20 #5 0x00004250 in 0x4250 #6 0x0000290c in 0x290c #7 0x00002414 in 0x2414 #8 0x00002a2c in 0x2a2c #9 0x90031c44 in mach_msg_server #10 0x00002c40 in 0x2c40 #11 0x00002f48 in 0x2f48 #12 0x00002188 in 0x2188 #13 0x00002008 in 0x2008 PPC Thread State: srr0: 0x000152a4 srr1: 0x0200d030 vrsave: 0x00000000 xer: 0x00000000 lr: 0x00015254 ctr: 0x90000f00 mq: 0x00000000 r0: 0x000017e8 r1: 0xbffff430 r2: 0x00000000 r3: 0x00172a78 r4: 0x00000003 r5: 0x00000001 r6: 0x00000040 r7: 0x00032230 r8: 0x00001680 r9: 0x00000014 r10: 0x00032230 r11: 0x0016c428 r12: 0x90000f00 r13: 0x000321b8 r14: 0x00032234 r15: 0x0000003f r16: 0x00001770 r17: 0x00001f80 r18: 0x00170c00 r19: 0x00000010 r20: 0x00032234 r21: 0x000321b8 r22: 0x00172630 r23: 0x00000030 r24: 0x00032230 r25: 0x01857c60 r26: 0x00032234 r27: 0x00172a48 r28: 0x00000033 r29: 0x00032230 r30: 0x00001680 r31: 0x00014914 Link to comment Share on other sites More sharing options...
bernarddesgagne Posted January 13, 2003 Author Report Share Posted January 13, 2003 Thank you for your post, Hugh. Link to comment Share on other sites More sharing options...
AmyJ Posted January 13, 2003 Report Share Posted January 13, 2003 We have successfully reproduced the fix_prebinding issue and will post information to the forum as it becomes available. We will be actively looking into this issue. Thank you for your patience. Amy Dantz Technical Support Link to comment Share on other sites More sharing options...
CallMeDave Posted January 13, 2003 Report Share Posted January 13, 2003 Did you choose to post 14 instances of the identical crash log information because you wanted everyone to know that it was happening often? A trip to Apple's support discussion area reveals others experiencing this process crashing in other situations. Sometimes on launching other applications (besides Retrospect), sometimes on log-in. This really sounds like an Apple bug, introduced with the 10.2.3 update. It's really polite to snip un-necessary information from public postings; a single example of your crash log (which isn't much help to developers without the debugging information that only Apple holds for this process) would have been more effective then posting the same text strings over and over. Dave Link to comment Share on other sites More sharing options...
mok Posted February 6, 2003 Report Share Posted February 6, 2003 I have to agree that the Greed approach to tech support (such as is practiced by Dantz and many other software companies, including Apple) is not only rude, but also arrogant. And I think the eventual result for these companies will be negative - at least I hope so. It is implicitly not fair to abandon customers after selling them software that is buggy, poorly-manualed, overly finicky, and actually still in development that requires frequent upgrades. Most people don't have clue as to how to get even half of what their computer is capable of out of the machine. That they may deserve such treatment is perhaps true, but only as long as they are not lured to the product with the promise that it's use is easy. The stampede for market share and profitability should not leave the customer behind. Link to comment Share on other sites More sharing options...
mok Posted February 6, 2003 Report Share Posted February 6, 2003 Dave - if I have to call you something, I think I'll be conservative and call you patronizing. I, too, have the fix_prebinding problem with Retrospect (which I described elsewhere). I finally caught on and did the search for "fix_prebinding" (with the dash instead of the space) and got this mess. Essentially, my fix_prebinding problem exhibits behavior almost identical to the French version, as delineated by Bernard. I do not get this crash performance with any other application. US English version of Retrospect 5.0.205, recently re-installed to no affect for the fix_prebinding problem. Machine configuration: US English MacOS 10.2.3 - G4 QuickSilver 867mhz - 1.5GB RAM - Apple-installed, partitioned IBM-IC35L060AVER07-0 60 GB HD - 120 GB Barracuda ST3120023A IDE single partition "slave" - 120 GB partitioned external FireWire Drive (fix_prebinding problem occurs also when this last drive is not mounted). Link to comment Share on other sites More sharing options...
mok Posted February 7, 2003 Report Share Posted February 7, 2003 I just installed Retrospect 5.0.238 English thusly: Uninstalled 5.0.205 with the installer, removed danz.plist pref, emptied trash, rebooted, installed 5.0.238, and before I could enter the serial number I got the following: RetroRun.crash.log Date/Time: 2003-02-06 17:51:15 -0600 OS Version: 10.2.3 (Build 6G30) Host: Patrick-McKelveys-Computer.local. Command: RetroRun PID: 512 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_INVALID_ADDRESS (0x0001) at 0x001e8c4c Thread 0 Crashed: #0 0x00003950 in GetPID (main.c:258) #1 0x000045c0 in main (main.c:577) #2 0x000031c8 in _start #3 0x00002ff8 in start PPC Thread State: srr0: 0x00003950 srr1: 0x0000d030 vrsave: 0x00000000 xer: 0x00000000 lr: 0x0000394c ctr: 0x90073c40 mq: 0x00000000 r0: 0x0000394c r1: 0xbffffad0 r2: 0x00143010 r3: 0x00000000 r4: 0x00000003 r5: 0x00000028 r6: 0x0000002c r7: 0x00000703 r8: 0x00000000 r9: 0x001e8c34 r10: 0x00000001 r11: 0xa0004894 r12: 0x90073c40 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000 r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000 r20: 0x00000000 r21: 0x00000000 r22: 0x00000000 r23: 0x00000000 r24: 0x00000000 r25: 0x00000000 r26: 0xbffffeb0 r27: 0x00000008 r28: 0x00000001 r29: 0xbffffebc r30: 0xbffffad0 r31: 0x000037c0 console.log Mac OS X Version 10.2.3 (Build 6G30) Feb 6 17:47:46 Patrick-McKelveys-Computer /sbin/autodiskmount[205]: disk2s1s2 hfs no no Ozark Wilderness Works [not mounted] Feb 6 17:47:47 Patrick-McKelveys-Computer /sbin/autodiskmount[205]: disk2s1s2 hfs no no Ozark Wilderness Works /Volumes/Ozark Wilderness Works Feb 6 17:47:49 Patrick-McKelveys-Computer DMProxy: theErr=-4200 [line 787, file DMProxy.c] Feb 6 17:47:49 Patrick-McKelveys-Computer DMProxy: theErr=-4200 [line 367, file DMProxy.c] Feb 6 17:47:49 Patrick-McKelveys-Computer DMProxy: theErr=-4200 [line 286, file DMProxy.c] 2003-02-06 17:47:50.050 iCal[468] unable to find Helvetica Neue font, using helvetica instead 2003-02-06 17:47:50.472 iCal[468] unable to find Helvetica Neue font, using helvetica instead 2003-02-06 17:47:57.894 QuicKeysKeyPressDaemon[484] QuicKeys keypress daemon running Feb 6 17:48:29 Patrick-McKelveys-Computer authexec: executing /Users/moky/.Trash/Retrospect/Contents/MacOS/AuthenticateUser.app/Contents/MacOS/../../../LaunchRetro Feb 6 17:48:52 Patrick-McKelveys-Computer authexec: executing /System/Library/Frameworks/Carbon.framework/Versions/Current/Support/LaunchCFMApp kill: usage: kill [-s sigspec | -n signum | -sigspec] [pid | job]... or kill -l [sigspec] Feb 6 17:49:43 Patrick-McKelveys-Computer crashdump: Crash report written to: /Library/Logs/CrashReporter/fix_prebinding.crash.log Feb 6 17:51:15 Patrick-McKelveys-Computer crashdump: Crash report written to: /Library/Logs/CrashReporter/RetroRun.crash.log fix-prebinding.crash.log Date/Time: 2003-02-06 17:49:43 -0600 OS Version: 10.2.3 (Build 6G30) Host: Patrick-McKelveys-Computer.local. Command: fix_prebinding PID: 472 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000054 Thread 0 Crashed: #0 0x000152a4 in 0x152a4 #1 0x0000c3d8 in 0xc3d8 #2 0x0000c0ec in 0xc0ec #3 0x0000b3ac in 0xb3ac #4 0x00007b20 in 0x7b20 #5 0x00004250 in 0x4250 #6 0x0000290c in 0x290c #7 0x00002414 in 0x2414 #8 0x00002a2c in 0x2a2c #9 0x90031c44 in mach_msg_server #10 0x00002c40 in 0x2c40 #11 0x00002f48 in 0x2f48 #12 0x00002188 in 0x2188 #13 0x00002008 in 0x2008 PPC Thread State: srr0: 0x000152a4 srr1: 0x0200f030 vrsave: 0x00000000 xer: 0x00000000 lr: 0x00015254 ctr: 0x90000f00 mq: 0x00000000 r0: 0x000017e8 r1: 0xbffff430 r2: 0x00000000 r3: 0x036baa78 r4: 0x00000003 r5: 0x00000001 r6: 0x00000040 r7: 0x00032230 r8: 0x00001680 r9: 0x00000014 r10: 0x00032230 r11: 0x036b4428 r12: 0x90000f00 r13: 0x000321b8 r14: 0x00032234 r15: 0x0000003f r16: 0x00001770 r17: 0x00001f80 r18: 0x036b8c00 r19: 0x00000010 r20: 0x00032234 r21: 0x000321b8 r22: 0x036ba630 r23: 0x00000030 r24: 0x00032230 r25: 0x05a5fc60 r26: 0x00032234 r27: 0x036baa48 r28: 0x00000033 r29: 0x00032230 r30: 0x00001680 r31: 0x00014914 NOTE: One of these - can't remember which - popped up AFTER Retrospect started up - the other two popped up before i coul;d even re-enter the serial number - i think console was one of these first. Link to comment Share on other sites More sharing options...
CallMeDave Posted February 7, 2003 Report Share Posted February 7, 2003 Quote: Uninstalled 5.0.205 with the installer, removed danz.plist pref, emptied trash, rebooted, installed 5.0.238, and before I could enter the serial number I got the following: Looking at your Console log it appears that your Mac was attempting to launch something inside your Trash folder: /Users/moky/.Trash/Retrospect/Contents/MacOS/AuthenticateUser.app/Contents/MacOS/../../../LaunchRetro It appears that you didn't get rid of everything before you installed fresh. As for the fix_prebinding crash, it's real, it seems to have begun with OS X 10.2.3, and it happens with other applications besides Retrospect (check the Apple support boards). AmyC has said that Dantz is looking into it, but I'd put my money on it being an Apple bug that needs to get squashed by the OS vendor. Dave Link to comment Share on other sites More sharing options...
mok Posted February 7, 2003 Report Share Posted February 7, 2003 Right! I looked in the trash and there was the discarded 5.0.205 application. I emptied the trash, started Retrospect 5.0.238 and NO CRASH LOGS APPEARED! THANKS! But........ I installed the 5.0 drivers - dialog asked about accessing old 4.3 scripts (wouldn't recognize these in the past under OSX) - I said SURE!............. and now I can't access the scripts I created under OSX with 5.0.205. The error message is the same one I used to get for 4.3 driver scripts created with OS9 - "? Retrospect version 5.0.238 launched at 2/7/2003 9:20 AM + Retrospect Driver Update, version 3.1.105 Run document Run 03 pvc Backup failed: Script 03 pvc Backup is not defined" How can I get Retrospect to AGAIN recognize these scripts defined in OS 10.2.3 with Retrospect 5.0.205? Not only that.... when I tried to launch Help for Retrospect 5.0.238, Classic booted and opened Navigator 4.7 - which I never use. Of course the help files accessed by this method were non-relevant. In fact, NOWHERE in the forums can I find a reference to "scripts not defined" or "undefined scripts". Nobody else seems to be having a problem with scripts not defined, but I have a lot of them, so I must be doing something dumb and obvious. But I have no idea what it is. WHAT IS GOING ON? Link to comment Share on other sites More sharing options...
mok Posted February 7, 2003 Report Share Posted February 7, 2003 Just had a thought. Can it be that when I uninstalled Retrospect 5.0.205, I also uninstalled the scripts I had created with it? Link to comment Share on other sites More sharing options...
AmyJ Posted February 7, 2003 Report Share Posted February 7, 2003 Quote: Just had a thought. Can it be that when I uninstalled Retrospect 5.0.205, I also uninstalled the scripts I had created with it? Yes. Link to comment Share on other sites More sharing options...
mok Posted February 8, 2003 Report Share Posted February 8, 2003 The fix_prebinding crashes that had been occuring have reappeared. So, as you replied, AmyC, perhaps I had deleted those scripts when I uninstalled Retrospect 5.0.205 preperatory to installing the update. Just now, I started Retrospect to recreate those scripts, and ...... BAM! As soon as I hit the Scripts button under Automate, the following fix_prebinding.crash.log appeared: Date/Time: 2003-02-08 10:17:08 -0600 OS Version: 10.2.3 (Build 6G30) Host: Patrick-McKelveys-Computer.local. Command: fix_prebinding PID: 732 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000054 Thread 0 Crashed: #0 0x000152a4 in 0x152a4 #1 0x0000c3d8 in 0xc3d8 #2 0x0000c0ec in 0xc0ec #3 0x0000b3ac in 0xb3ac #4 0x00007b20 in 0x7b20 #5 0x00004250 in 0x4250 #6 0x0000290c in 0x290c #7 0x00002414 in 0x2414 #8 0x00002a2c in 0x2a2c #9 0x90031c44 in mach_msg_server #10 0x00002c40 in 0x2c40 #11 0x00002f48 in 0x2f48 #12 0x00002188 in 0x2188 #13 0x00002008 in 0x2008 PPC Thread State: srr0: 0x000152a4 srr1: 0x0200d030 vrsave: 0x00000000 xer: 0x00000000 lr: 0x00015254 ctr: 0x90000f00 mq: 0x00000000 r0: 0x000017e8 r1: 0xbffff430 r2: 0x00000000 r3: 0x00172a78 r4: 0x00000003 r5: 0x00000001 r6: 0x00000040 r7: 0x00032230 r8: 0x00001680 r9: 0x00000014 r10: 0x00032230 r11: 0x0016c428 r12: 0x90000f00 r13: 0x000321b8 r14: 0x00032234 r15: 0x0000003f r16: 0x00001770 r17: 0x00001f80 r18: 0x00170c00 r19: 0x00000010 r20: 0x00032234 r21: 0x000321b8 r22: 0x00172630 r23: 0x00000030 r24: 0x00032230 r25: 0x01857c60 r26: 0x00032234 r27: 0x00172a48 r28: 0x00000033 r29: 0x00032230 r30: 0x00001680 r31: 0x00014914 I don't know what it means, but I usually try to avoid msg, no matter who is serving it - it's bad for you. Maybe this set of circumstances will provide a clue. Link to comment Share on other sites More sharing options...
CallMeDave Posted February 9, 2003 Report Share Posted February 9, 2003 Quote: As soon as I hit the Scripts button under Automate, the following fix_prebinding.crash.log appeared: The timing is just a coincidence. Whatever the cause of the fix_prebinding crash, it seems to occur some time _after_ Retrospect launches. It doesn't matter what you do, or don't do, inside Retrospect. If this process is gonna crash, it's gonna crash no matter what. As for the crash.log file, those things don't do much good unless the process that's running has de-bug information in its code. I'm still betting that Apple is going to solve this one in Cupertino. Dave Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.