Segfault 11 on startup about packr HOT 16 CLOSED

Hi @petriborg ,

Any update on this issue? We have one user report for our game (released just yesterday) who's crash log looks very similar. I have no idea yet about how to resolve that.

edit: partial crash log:

OS Version: Mac OS X 10.7.5 (11G63)

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_PROTECTION_FAILURE at 0x00007fff5fc01028

Unknown thread crashed with X86 Thread State (64-bit):
rax: 0x0000000000000055 rbx: 0x0000000000000000 rcx: 0x0000000000000000 rdx: 0x0000000000000000
rdi: 0x0000000000000000 rsi: 0x0000000000000000 rbp: 0x0000000000000000 rsp: 0x0000000000000000
r8: 0x0000000000000000 r9: 0x0000000000000000 r10: 0x0000000000000000 r11: 0x0000000000000000
r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000
rip: 0x00007fff5fc01028 rfl: 0x0000000000010203 cr2: 0x00007fff5fc01028
Logical CPU: 1

from packr.

@code-disaster: Actually yes, I realized this morning that the mac binary that is included in the source is fubar. I needed to install premake4 (I did so via port install premake4), then run packr/native/build-mac.sh, this built mew a new Mac executable which works on my Mac...

But I suspect that this means there is actually some problem with the Mac code or its complication flags that make it incompatible between some versions? Which would be a problem, obviously.

from packr.

Interesting. Would make sense, as the packr-mac in Git was last compiled on my machine.

Would you mind send me your executable to codi at code-disaster dot com? I'd like to check if it would run here.

from packr.

You should have it in the mail now. I will note that I also got to test on a Windows box and had a similar problem, but I don't know enough about Windows debugging to be of use. It worked out of the box on Linux Ubuntu 10.04 64-bit.

from packr.

Thanks! It works here, so I guess now we only have to find out how to get it properly compiled on newer OS X versions (I run 10.9). :)

from packr.

Adding "-mmacosx-version-min=10.6" to both compiler and linker options seems to do the trick.

from packr.

I have the same problem under Mac OS X 10.6.8 with this kind of Mac Book Pro:
http://www.everymac.com/systems/apple/macbook_pro/specs/macbook-pro-core-2-duo-2.4-15-santa-rosa-specs.html

@code-disaster Thanks for the trick :) Maybe we should rather rely on a shell script instead of an executable like in this example:
http://www.youtube.com/watch?v=Unl8dgqFv6o

@petriborg Using a Windows shell script within a MSI package might help to work around with those problems with binaries. I prefer using RPM/DEB packages under GNU Linux. Packr has been very helpful for me under Mac anyway.

Edit.: I don't know how to make a single file from my directory. If I make a ZIP archive with it, it is no longer recognized as an .app "file".

Edit.2: Please can one of you fork the repository and push the recompiled launcher so that everybody can benefit of it?

from packr.

@gouessej Sure no problem. Done.

from packr.

@petriborg Thank you very much. I'm going to give it a try in a few hours :)

from packr.

It still crashes but that's probably not because of Packr:
http://sourceforge.net/p/tuer/tickets/9/#274a

from packr.

The callstack of thread 1 looks like it crashed while trying to get access to your main method. Hard to tell if its a configuration issue or some other problem.

from packr.

I think that the OpenJDK build I use is probably incompatible with this version of Mac. I'm uploading my application bundle but it takes a lot of time :s

from packr.

My zipped application bundle is here: http://tuer.sourceforge.net/very_experimental/tuer.app.zip

It would be nice if someone with a more recent version of Mac than me could give it a try.

from packr.

I get those error messages when running on Mac OS X 10.6.8:
2014-07-27 20:17:47.441 TUER[400:1303] *** NSInvocation: warning: object 0x107ef53c0 of class 'ThreadUtilities' does not implement methodSignatureForSelector: -- trouble ahead
2014-07-27 20:17:47.444 TUER[400:1303] *** NSInvocation: warning: object 0x107ef53c0 of class 'ThreadUtilities' does not implement doesNotRecognizeSelector: -- abort

Are you sure it can work with this version?

from packr.

Its been a while since I've used Objective-C, but I thought that it would fail to compile if it wasn't compatible. What happens when you run the build-mac.sh script?

from packr.

Actually, the error messages above are displayed in the console when I run the executable (the launcher) inside the Mac application bundle under OS X 10.6.8. Someone else succeeded in running my application under OS X 10.9.4. The reason is simple, it comes from OpenJDK 7 which isn't supported by OS X 10.6.8 since the update 40 or earlier (it should work with the update 25). Sorry for making you waste your time.

from packr.