Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Segfault 11 on startup #21

Closed
petriborg opened this issue Jul 16, 2014 · 16 comments
Closed

Segfault 11 on startup #21

petriborg opened this issue Jul 16, 2014 · 16 comments

Comments

@petriborg
Copy link

I'm trying to create a test application using packr, but when I try to launch the app it crashes out with a segmentation fault 11. I tried it with the bit.ly linked packr.jar and with a freshly built from the git repo.

This is the json file:
{
"platform": "mac",
"jdk": "openjdk-1.7.0-u60-unofficial-macosx-x86_64-image.zip",
"executable": "test-packr",
"appjar": "dist/test-packr.jar",
"mainclass": "test/packr/TestPackr",
"vmargs": [
"-Xmx1G"
],
"outdir": "mac-test-packr.app"
}

This is the crash report:

Process: launchd [958]
Path: /Users/USER/*/mac-test-packr.app/Contents/MacOS/test-packr
Identifier: com.yourcompany.identifier
Version: ??? (???)
Code Type: X86-64 (Native)
Parent Process: launchd [223]

Date/Time: 2014-07-16 10:15:11.561 -0400
OS Version: Mac OS X 10.7.5 (11G63)
Report Version: 9

Interval Since Last Report: 195531 sec
Crashes Since Last Report: 25
Per-App Crashes Since Last Report: 11

Crashed Thread: Unknown

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

Backtrace not available

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: 2

Binary images description not available

External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 1
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 5194
thread_create: 1
thread_set_state: 0

Model: MacBookPro10,1, BootROM MBP101.00EE.B02, 4 processors, Intel Core i7, 2.6 GHz, 16 GB, SMC 2.3f36
Graphics: NVIDIA GeForce GT 650M, NVIDIA GeForce GT 650M, PCIe, 1024 MB
Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In, 512 MB
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D5434314753364D465238432D50422020
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D5434314753364D465238432D50422020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xEF), Broadcom BCM43xx 1.0 (5.106.198.19.22)
Bluetooth: Version 4.0.8f17, 2 service, 18 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
Serial ATA Device: APPLE SSD SM512E, 500.28 GB
USB Device: hub_device, 0x8087 (Intel Corporation), 0x0024, 0x1a100000 / 2
USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x8510, 0x1a110000 / 3
USB Device: hub_device, 0x8087 (Intel Corporation), 0x0024, 0x1d100000 / 2
USB Device: hub_device, 0x0424 (SMSC), 0x2512, 0x1d180000 / 3
USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0262, 0x1d182000 / 5
USB Device: BRCM20702 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x1d181000 / 4
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8286, 0x1d181300 / 7

@code-disaster
Copy link
Member

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

@petriborg
Copy link
Author

@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.

@code-disaster
Copy link
Member

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.

@petriborg
Copy link
Author

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.

@code-disaster
Copy link
Member

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). :)

@code-disaster
Copy link
Member

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

@ghost
Copy link

ghost commented Jul 24, 2014

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?

petriborg pushed a commit to petriborg/packr that referenced this issue Jul 25, 2014
@petriborg
Copy link
Author

@gouessej Sure no problem. Done.

badlogic added a commit that referenced this issue Jul 25, 2014
issue #21 fix - setting MacOSX 10.6 as target build
@ghost
Copy link

ghost commented Jul 25, 2014

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

@ghost
Copy link

ghost commented Jul 25, 2014

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

@code-disaster
Copy link
Member

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.

@ghost
Copy link

ghost commented Jul 25, 2014

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

@ghost
Copy link

ghost commented Jul 25, 2014

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.

@ghost
Copy link

ghost commented Jul 27, 2014

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?

@petriborg
Copy link
Author

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?

@ghost
Copy link

ghost commented Jul 28, 2014

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants