Opened 4 years ago
Last modified 4 years ago
#62749 new defect
Pallet crashes
Reported by: | macuserguru | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | macuserguru | |
Port: | Pallet |
Description
If I want start Pallet crashes permanently. I that known for the older Mac OS X 10.11.6 ElCapitan?
Process: Pallet [2037] Path: /Applications/MacPorts/Pallet.app/Contents/MacOS/Pallet Identifier: org.macports.Pallet Version: 1.0 Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: Pallet [2037] User ID: 503 Date/Time: 2021-04-25 12:44:02.755 +0200 OS Version: Mac OS X 10.11.6 (15G22010) Report Version: 11 Anonymous UUID: ...... Time Awake Since Boot: 14000 seconds System Integrity Protection: enabled Crashed Thread: 6 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY VM Regions Near 0: --> __TEXT 000000010b2c3000-000000010b2ca000 [ 28K] r-x/rwx SM=COW /Applications/MacPorts/Pallet.app/Contents/MacOS/Pallet
Change History (5)
comment:1 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)
Keywords: | Pallet crashes removed |
---|---|
Port: | Pallet added |
comment:2 Changed 4 years ago by kencu (Ken)
pallet on MP is in rough shape. See about 16 other open tickets.
This version will build on systems up to about 10.11 and at least put some output up, but still doesn't quite work so I haven't pushed it.
https://github.com/kencu/pallet/tree/fixpallet
To get it to build on the newest systems requires enabling some features like gc that require code changes I haven't got into.
comment:3 Changed 4 years ago by macuserguru
Ken, I was afraid that Pallet has problems under ElCapitan, also a reason why I have not attached the entire error message, but wanted to clarify this before. I've been able to get by without Pallet, but it's new to me, so I wanted to give it a try for the sake of testing.
comment:5 Changed 4 years ago by ryandesign (Ryan Carsten Schmidt)
Please attach the entire crash log so that we can figure out whether this is a duplicate of an existing ticket or a new problem.
Is that the entire crash log? It doesn't really say anything about why it crashed.