On Mon, 2018-05-07 at 22:30 +0100, Julian Smith wrote: > On Mon, 07 May 2018 16:06:10 +0100 > Richard Shann <[email protected]> wrote: > > > On Mon, 2018-05-07 at 14:21 +0000, Jeremiah Benham wrote: > > > > [..] > > > > > after updating to High Sierra 10.13.3. > > > > > > > > Jeremiah - I see you have a build dated 27th March 2018 > > > > > > > > http://www.denemo.org/~jjbenham/darwin/denemo-0.0.0-0-darwin-x6 > > > > 4.ta > > > > r.bz > > > > 2 > > > > > > Yes. They should. > > > > Hmm, Julian - I hope you noticed that the URL I gave before had > > gotten > > split by a newline > > > > http://www.denemo.org/~jjbenham/darwin/denemo-0.0.0-0-darwin-x64.ta > > r.bz2 > > > > with the 2 on the end is correct. Please report back if this gives > > any > > problems as we are about to release this as Denemo version 2.3 > > Thanks for this. > > But i'm afraid after jumping through a bunch of hoops > to persuade Mac OS to run the the new binary (they seem to have > tightened up the security for unofficial apps) the same thing happens > - we > get a crash on startup with the following info: > > Process: denemo [1059] > Path: /private/var/folders/*/Denemo.app/Contents/Mac > OS/../Resources/bin/denemo > Identifier: org.denemo > Version: 1.0 (1) > Code Type: X86-64 (Native) > Parent Process: ??? [1] > Responsible: denemo [1059] > User ID: 501 > > Date/Time: 2018-05-07 21:51:54.338 +0100 > OS Version: Mac OS X 10.13.3 (17D47) > Report Version: 12 > Anonymous UUID: 2F861B95-2F93-A752-8E81-64A1BA5B0018 > > > Time Awake Since Boot: 2900 seconds > > System Integrity Protection: enabled > > Notes: Translocated Process > > Crashed Thread: 0 Dispatch queue: com.apple.main-thread > > Exception Type: EXC_CRASH (SIGABRT) > Exception Codes: 0x0000000000000000, 0x0000000000000000 > Exception Note: EXC_CORPSE_NOTIFY > > Application Specific Information: > abort() called > > Thread 0 Crashed:: Dispatch queue: com.apple.main-thread > 0 libsystem_kernel.dylib 0x00007fff78058e3e > __pthread_kill + 10 > 1 libsystem_pthread.dylib 0x00007fff78197150 > pthread_kill + 333 > 2 libsystem_c.dylib 0x00007fff77fb5312 abort + > 127 > 3 denemo 0x000000010ca72400 > main_log_handler + 656 > 4 libglib-2.0.0.dylib 0x000000010dbeab7d g_logv + > 874 > 5 libglib-2.0.0.dylib 0x000000010dbea7fe g_log + > 134 > 6 denemo 0x000000010ca72ab4 > process_command_line + 1700 > 7 denemo 0x000000010ca7212b main + > 139 > 8 libdyld.dylib 0x00007fff77f09115 start + > 1 > > Thread 1: > 0 libsystem_kernel.dylib 0x00007fff78059562 > __workq_kernreturn + 10 > 1 libsystem_pthread.dylib 0x00007fff7819406a > _pthread_wqthread + 1035 > 2 libsystem_pthread.dylib 0x00007fff78193c4d > start_wqthread + 13 > > Thread 2: > 0 libsystem_kernel.dylib 0x00007fff78059562 > __workq_kernreturn + 10 > 1 libsystem_pthread.dylib 0x00007fff7819426f > _pthread_wqthread + 1552 > 2 libsystem_pthread.dylib 0x00007fff78193c4d > start_wqthread + 13 > > Thread 3: > 0 libsystem_pthread.dylib 0x00007fff78193c40 > start_wqthread + 0 > 1 ??? 0x00000a3e7473696c 0 + > 11263357970796 > > Thread 4: > 0 libsystem_kernel.dylib 0x00007fff78059562 > __workq_kernreturn + 10 > 1 libsystem_pthread.dylib 0x00007fff7819406a > _pthread_wqthread + 1035 > 2 libsystem_pthread.dylib 0x00007fff78193c4d > start_wqthread + 13 > > Thread 0 crashed with X86 Thread State (64-bit): > rax: 0x0000000000000000 rbx: 0x00007fffb0c33340 rcx: > 0x00007ffee3218308 rdx: 0x0000000000000000 > rdi: 0x0000000000000307 rsi: 0x0000000000000006 rbp: > 0x00007ffee3218340 rsp: 0x00007ffee3218308 > r8: 0x9e3779b97f4a7c55 r9: 0x0000000000000004 r10: > 0x0000000000000000 r11: 0x0000000000000206 > r12: 0x0000000000000307 r13: 0x000000010ca72170 r14: > 0x0000000000000006 r15: 0x000000000000002d > rip: 0x00007fff78058e3e rfl: 0x0000000000000206 cr2: > 0x00007fffb0c11148 > > Logical CPU: 0 > Error Code: 0x02000148 > Trap Number: 133 > > > The backtraces in this report seem very similar if not identical to > the > ones from 2.2.0, but the line for the binary itself differs: > > For 2.2.0: > 0x100205000 - 0x1003bdfff +denemo (0) <E609C47F-BF78- > 3230-8700-7D3B5CF714F8> > /var/folders/*/Denemo.app/Contents/Resources/bin/denemo > > And for denemo-0.0.0-0-darwin-x64.tar.bz2: > > 0x100205000 - 0x1003bdfff +denemo (0) <E609C47F-BF78- > 3230-8700-7D3B5CF714F8> > /var/folders/*/Denemo.app/Contents/Resources/bin/denemo >
Thanks for taking the trouble to report back on this, it seems there is more work to be done to get it working. BTW I wasn't able to see a difference in the output you posted, but it's unimportant as it is too low level to give any clue as to the problem (which I had a hint might be to do with where the newer Mac stores fonts). Richard _______________________________________________ Denemo-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/denemo-devel
