You are viewing an historical archive of past issues. Please report new issues to the appropriate project issue tracker on GitHub.

Bug #389: Error -100 on launch (causes Synergy Advance to exit immediately)

Kind bug
Product Synergy Advance
When Created , updated
Status closed
Reporter froodiantherapy
Tags no tags

Description

Hi Wincent. As I mentioned in Bug 387, Synergy Advance crashes immediately upon launch (just bounces a few times in Dock, and then acts like I never launched it). Console.app reports "Error -100". I've tried redownloading, and this continues to happen.

As much information as could be relevant about my system: I'm on a PPC running 10.4.5 and iTunes 6.0.4. I have Synergy installed too (though not running). I also use Quicksilver (and its iTunes plugin).

If I move ~/Library/Preferences/com.wincent.SynergyAdvance.plist, the launch gets a bit further - a splash screen of some sort flashes across the screen, but then Synergy Advance immediately crashes (with the same log error).

If I go back to preview release .3, Synergy Advance works as expected.

Comments

  1. Greg Hurrell

    Ok, thanks for the info Ian. Are you aware of anything on your system that might be altering the Synergy Advance binary? ie. have you run any stripping or rebinding tools on it?

    I may have to send you a new build with a bunch of logging statements in it so that we can find out at exactly what point the anti-corruption tests are failing.

  2. froodiantherapy

    Hi Wincent. No, I don't know of anything that would have altered my Synergy Advance binary. I'd be happy to run a logging build.

  3. Greg Hurrell

    Ok, I've put a new build up on the server that includes logging statements at every point in the program where a -100 error might be produced. If you can run this and let me know what gets printed to the console then it will help me know exactly where the failure is occurring.

    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

  4. froodiantherapy

    Hi Wincent, console says

    2006-04-01 11:01:50.925 Synergy Advance[28337] **** 8: NO, YES

    and then gives the -100 error

  5. Greg Hurrell

    Thanks for reporting back, Ian. What this tells us is that it's getting right to the end of the anti-corruption test and at the final step it encounters a mismatch between the checksum it *calculates* for the binary and the checksum that it *expects* to find.

    So I am not sure exactly why the checksum is wrong (you say there's nothing altering the binary), but it may be related to bug #387 (once again in the anti-corruption code, although in that case it's actually crashing rather than aborting with an error).

    Something very odd is going on because this code has been in place and working since the very first public release (back in May 2005), I haven't made any changes to that code, and it has always worked for me on both PowerPC and Intel, right up to the current version of Mac OS X (I'm currently running 10.4.5 on a G5); evidently *something* has changed in Mac OS X that is causing this to break for *some* users, but only when running the 0.4 beta, not the previous one. So in summary we have three variables: (1) a bunch of different versions of Mac OS X; (2) a couple of different versions of Synergy Advance; (3) a bunch of different users. It appears that some specific combinations of (1), (2) and (3) are experiencing problems, but the pattern is far from clear at this stage.

    It's beginning to look like I may just have to switch off these anti-corruption checks entirely and hope that there are no problems down the road as a result later on. The reason I developed all this stuff is that Synergy (http://wincent.dev/) has been hacked and cracked and tampered with so widely that I didn't want users being exposed to the risk of running versions that have been altered by untrusted third parties (trojans, spyware etc). This is why it's important to always download only from the wincent.dev website and never trust a copy obtained from another source.

    As I mention in that other bug I already have an alternative mechanism in place so I may just have to abandon this one and switch over. I don't like doing that because I invested a lot of time in developing this stuff, but it looks like it may just be too fragile and brittle. In any case, I'll post notification here once I have a new build available.

  6. Greg Hurrell

    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.

  7. Greg Hurrell

    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.

  8. froodiantherapy

    Hi Wincent. Just wanted to confirm that this WFM now. Thanks for the fast fix! :)

Add a comment

Comments are now closed for this issue.

Menu