Bug #387: Crash upon launch

Comments

1. Greg Hurrell 2006-03-29T11:44:51Z

   Anything printed to the console at launch time? What kind of system are you running on? (Intel by any chance?)

2. bugzilla user 328 2006-03-29T12:03:20Z

   the only thing I see when I start it up is a very brief splash screen (maybe 2 seconds) and then the error triangle (I assume) and then it quits. I posted a screen shot to the other thread that you said to send replies to if a bug is found.

   Oh and I am running on a g4 12" 1.5 GHz PB with 1.25 GB ram G4

   Hope this helps

3. Greg Hurrell 2006-03-29T12:06:41Z

   But is anything printed to the console at launch time? You can find the console at:

   /Applications/Utilities/Console.app

   That will hopefully give us some clue as to *why* it's failing to launch.

4. bugzilla user 328 2006-03-29T12:15:16Z

   Here is what I found in the console

   2006-03-29 14:12:40.790 Wincent Crash Reporter[492] Error: no bundle argument [exiting]

   hope that helps

5. froodiantherapy 2006-03-29T16:26:53Z

   Hi Wincent. I get this behavior as well. Console.log says

   2006-03-29 17:15:53.290 Synergy Advance[17640] Error -100: please inform the developer

   Since this is a differenct error than JB got, I'm not sure that it's the same issue; I can file seperately if you wish. Also, I'm not sure if this is relevant, but when I first copied Synergy Advance from the disk image, Finder crashed (I can post the crash log if you think it is).

6. Greg Hurrell 2006-03-29T17:38:06Z

   Ian, that error (-100) indicates file corruption. Either the file is corrupt (perhaps that Finder crash you mentioned?) or Synergy Advance *thinks* it's corrupt (in which case we have a bug). If you see the same error after re-doing the copy please open a separate bug report and we'll try to figure out exactly why Synergy Advance thinks it's been corrupted (provide as much info as possible about your system configuration).

7. Greg Hurrell 2006-03-30T02:00:02Z

   See bug #389 for the "Error -100" issue.

8. bugzilla user 328 2006-03-30T11:04:10Z

   Oh just a follow up. I found the .3 release and installed that instead and I have had no problems so far. Synergy adv works like it is supposed to, no crashes, etc.

9. Greg Hurrell 2006-03-30T11:40:09Z

   (In reply to comment #0)

   In addition when looking for the crashlog, one does not exist in ~/library/logs

   Just to clarify: you *were* looking in "~/Library/Logs/CrashReporter/", right? Not "~/library/logs"?

10. bugzilla user 328 2006-03-30T12:18:24Z

    That is correct... I did look within ~/library/logs/crashreporter/ and there was no report from synergy

11. Greg Hurrell 2006-04-01T06:53:45Z

    Ok, I've put a new build (0.4b2) up on the server. This version won't fix the crashes but it should help to diagnose them because the crash reporter application is once again functional. The idea is that each time Synergy Advance launches it checks to see if it shut down cleanly on the last run. If it did not then it offers to send a crash report. In order for this to work then you must do a least one successful launch (so that Synergy Advance can write a timestamp to its preferences file); in the case where it never ever launches successfully you still won't see the crash reporter, but at least now crash logs should be written to the CrashReporter logs directory and you'll be able to attach them here (the older version was catching crashes and that prevented the logs from being written).

    To gather more information it is also useful to capture all console output. One way of capturing all the console output is to run the program from the Terminal; for example, assuming you installed the app into "/Applications/" you would do:

    cd "/Applications/Synergy Advance.app/Contents/MacOS" "./Synergy Advance"

    Announcement:

    https://wincent.dev/a/news/archives/2006/04/synergy_advance_5.php

    SHA1 checksum:

    e2e537d178e62c13d2846aed9c49f61ea3cf1c93

12. bugzilla user 328 2006-04-01T07:18:06Z

    Where should I email you a copy of the crash log?

13. Greg Hurrell 2006-04-01T07:56:59Z

    (In reply to comment #12)

    Where should I email you a copy of the crash log?

    You can attach it directly to this bug report (click on the "Create New Attachment" link) or email it to me directly and I'll attach it myself. Thanks.

14. bugzilla user 328 2006-04-01T08:41:31Z

    Created an attachment (id=54) Crash Log

    Crash Log for synergy advance

15. Greg Hurrell 2006-04-01T09:03:51Z

    (From update of attachment 54) Changing attachment MIME type to text/plain

16. Greg Hurrell 2006-04-01T09:38:06Z

    Thanks very much for attaching the crash report. I now see exactly where the crash is occurring. It seems that NSTask is raising an exception (perhaps because of a file-not-found error? It's trying to launch the "/usr/bin/redo_prebinding" tool: does that exist on your system?). Anything printed to the console at that moment? I imagine there should be because the stack trace shows:

    +[NSException raise:format:]

    I've now added a @try/@catch around the offending part of the code which means that Synergy Advance won't crash anymore when this happens, but it will still throw an error (the same one as in bug #389) so I may have to look at dropping the executable self-checking. I have an alternative for guarding against executable corruption already in place any way so I may just swap that in.

17. Greg Hurrell 2006-04-01T13:18:34Z

    OK, I've now officially deactivated the anti-corruption checks and removed the code. Adding the fixed-in-prerelease keyword. Will put together a 0.4b3 release shortly.

18. Greg Hurrell 2006-04-03T04:35:19Z

    Version 0.4b3 is now on the servers and available for download. For more information see:

    https://wincent.dev/a/news/archives/2006/04/synergy_advance_6.php

    Marking as FIXED/CLOSED.

19. bugzilla user 328 2006-04-03T05:21:16Z

    just FYI crashed at startup again. I'm emailing you a copy of the crash log via the crash reporter.

20. Greg Hurrell 2006-04-03T05:54:17Z

    Please upgrade to the just-released version. The crash report you just sent me is for the old version.

Add a comment

Comments are now closed for this issue.