[Unison-hackers] Mac update

[Alan Shutko]

I’ve done some research on this.  This seems like it might be possibly relevant:

http://stackoverflow.com/questions/20114920/can-an-exec-bad-instruction-sigill-on-dyld-my-fault

Marcus, how is your build setup? Is it possible there is a difference between the way certain libraries were built? It seems like we might get a SIGILL as shown in your crash if we have some parts compiled for 32-bit and others for 64-bit (or other arch differences).  In UISTYLE=text, all the build arguments are controlled by the makefile. In UISTYLE=uimac* the flags for compiling the objective C stuff is in the xcode project.

Three questions: could you send me a log of your compilation?  

Are you using the new version on both the local and remote system?

If so, is it crashing on the local system, the remote, or both?


> On Jul 8, 2014, at 2:22 AM, Marcus Crestani <crestani at informatik.uni-tuebingen.de> wrote:
> 
>>>>>> "BCP" == Benjamin C Pierce <bcpierce at cis.upenn.edu> writes:
> BCP> Unless I hear about any problems in the next couple days, I’ll make
> BCP> a new beta-release out of it.
> 
> Thanks, it builds and works fine, except the problem with the new OS X
> port (UISTYLE=uimac14) I've reported earlier:
> 
>  http://lists.seas.upenn.edu/pipermail/unison-hackers/2014-May/001704.html
> 
> As expected, the crash is identical and 100% reproducible for me and
> does not occur when using the UISTYLE=gtk2 or the UISTYLE=text builds.
> 
> Keep up the good work,
> 
> -- 
> Marcus
> _______________________________________________
> Unison-hackers mailing list
> Unison-hackers at lists.seas.upenn.edu
> http://lists.seas.upenn.edu/mailman/listinfo/unison-hackers

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.seas.upenn.edu/pipermail/unison-hackers/attachments/20140717/eaa52927/attachment.html>