Jump to content

retrospect quits suddenly during preview


Recommended Posts

I can not complete a backup. At some point during the index, retrospect just up and quits with nary a peep. Any ideas on the fix? I have re-installed, with the same effect. I am using the most current version of retrospect and drivers, and Mac OS X 10.5.5 (9F33). I found this in the console log after trying a few times to get it to run:

 

10/19/08 12:33:48 AM Retrospect[1103] Retrospect(1103,0xa089c074)

malloc: *** error for object 0x1e5450: incorrect checksum for freed

object - object was probably modified after being freed.

*** set a breakpoint in malloc_error_break to debug

 

10/19/08 12:33:48 AM [0x0-0xf30f3].AuthenticateUser

Retrospect(1103,0xa089c074) malloc: *** error for object 0x1e5450:

incorrect checksum for freed object - object was probably modified

after being freed.

 

10/19/08 12:33:49 AM ReportCrash[1116] Formulating crash report for

process Retrospect[1103]

 

10/19/08 12:33:49 AM ReportCrash[1116] Saved crashreport to

/Library/Logs/CrashReporter/Retrospect_2008-10-19-003349_Leopold.crash

using uid: 0 gid: 0, euid: 0 egid: 0

 

10/19/08 12:35:08 AM Retrospect[1121] Retrospect(1121,0xa089c074)

malloc: *** error for object 0x1e7e90: incorrect checksum for freed

object - object was probably modified after being freed.

*** set a breakpoint in malloc_error_break to debug

 

10/19/08 12:35:08 AM [0x0-0xf70f7].AuthenticateUser

Retrospect(1121,0xa089c074) malloc: *** error for object 0x1e7e90:

incorrect checksum for freed object - object was probably modified

after being freed.

 

10/19/08 12:35:08 AM ReportCrash[1133] Formulating crash report for

process Retrospect[1121]

 

10/19/08 12:35:08 AM ReportCrash[1133] Saved crashreport to

/Library/Logs/CrashReporter/Retrospect_2008-10-19-003508_Leopold.crash

using uid: 0 gid: 0, euid: 0 egid: 0

 

10/19/08 12:44:13 AM ReportCrash[1174] Formulating crash report for

process Retrospect[1154]

 

10/19/08 12:44:14 AM ReportCrash[1174] Saved crashreport to

/Library/Logs/CrashReporter/Retrospect_2008-10-19-004413_Leopold.crash

using uid: 0 gid: 0, euid: 0 egid: 0

 

Here is the beginning of the crash report:

Process: Retrospect [1268]

Path: /Applications/Retrospect

6.1/Retrospect.app/Contents/MacOS/AuthenticateUser.app/Contents/MacOS/../../../Retrospect

Identifier: Retrospect

Version: ??? (???)

Code Type: PPC (Translated)

Parent Process: launchd [1]

 

Date/Time: 2008-10-19 08:12:31.046 -0700

OS Version: Mac OS X 10.5.5 (9F33)

Report Version: 6

 

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x000000006dde65c7

Crashed Thread: 0

 

Link to comment
Share on other sites

It's possible that Retrospect's configuration file is corrupt.

 

With Retrospect not running, drag the file Retro.Config from the folder /Library/Preferences/Retrospect to the desktop. Launch Retrospect (you'll need to re-enter your license code) and try scanning the volume again. If this works, you'll need to recreate your scripts, custom selectors, and lists, unless you have a good backup copy of Retro.Config.

Link to comment
Share on other sites

I am using the most current version of retrospect and drivers, and Mac OS X 10.5.5 (9F33).

Realize that these forums are not just for you, but for others who come behind you trying to see if their problem is solved by your solution. It would be helpful for posterity, because these threads persist for much longer than the "most current version" (whatever that is), if you would provide your Retrospect version and RDU version as printed in the Retrospect log on each launch.

 

It would also be helpful if some details were provided as to your hardware.

 

That said, have you tried changing the preference in Retrospect so that ACLs are not being backed up? There is a bug in Apple's Carbon API (which older code base programs, like Retrospect, currently use) that might be causing your issue.

 

Russ

Link to comment
Share on other sites

That said, have you tried changing the preference in Retrospect so that ACLs are not being backed up? There is a bug in Apple's Carbon API (which older code base programs, like Retrospect, currently use) that might be causing your issue.

Russ

 

Well that fixed it. Thanks!

 

Unfortunately, Retrospect does not seem to use my DL DVDs as double layer. Sigh.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...