-
Notifications
You must be signed in to change notification settings - Fork 4
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
update ci.yml to account for arm64 macos #48
base: master
Are you sure you want to change the base?
Conversation
Backtrace: libunwind: _Unwind_Resume(ex_obj=0x600001c10060)
libunwind: __unw_init_local(cursor=0x16fdfe140, context=0x16fdfe3b0)
libunwind: unwind_phase2(ex_obj=0x600001c10060)
libunwind: __unw_step_stage2(cursor=0x16fdfe140)
libunwind: __unw_get_reg(cursor=0x16fdfe140, regNum=-2, &value=0x16fdfdec0)
libunwind: __unw_get_proc_info(cursor=0x16fdfe140, &info=0x16fdfde78)
libunwind: __unw_get_proc_name(cursor=0x16fdfe140, &buf=0x16fdfdec8, bufLen=512)
libunwind: unwind_phase2(ex_obj=0x600001c10060): start_ip=0x100019df8, func=_ZL8nimFrameP7TFrame_, sp=0x16fdfe5f0, lsda=0x100032b34, personality=0x194ebd1ec
Process 26453 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=261, address=0xdac11410)
frame #0: 0x00000001a2a9792c libunwind.dylib`_Unwind_GetIP + 224
libunwind.dylib`_Unwind_GetIP:
-> 0x1a2a9792c <+224>: autib x16, x0
0x1a2a97930 <+228>: mov x17, x16
0x1a2a97934 <+232>: xpaci x17
0x1a2a97938 <+236>: cmp x16, x17
Target 0: (test2) stopped.
(lldb) bt
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=261, address=0xdac11410)
* frame #0: 0x00000001a2a9792c libunwind.dylib`_Unwind_GetIP + 224
frame #1: 0x0000000194ebd424 libc++abi.dylib`__gxx_personality_v0 + 568
frame #2: 0x000000010002cd88 test2`unwind_phase2(uc=<unavailable>, cursor=0x000000016fdfe140, exception_object=0x0000600001c10060) at UnwindLevel1.c:283:11 [opt]
frame #3: 0x000000010002cf94 test2`_Unwind_Resume(exception_object=0x0000600001c10060) at UnwindLevel1.c:492:5 [opt]
frame #4: 0x000000010001ac9c test2`f3__test50_u3(i_p0=3) at test2.nim:0:371
frame #5: 0x000000010001b5d4 test2`f2__test50_u135(i_p0=1) at test2.nim:41:115
frame #6: 0x000000010001b8c0 test2`f1__test50_u139() at test2.nim:46:23
frame #7: 0x000000010001b9d4 test2`NimMainModule() at test2.nim:50:193
frame #8: 0x000000010001b944 test2`NimMainInner() at test2.nim:74:2
frame #9: 0x000000010001c04c test2`NimMain() at test2.nim:85:2
frame #10: 0x000000010001c098 test2`main(argc=1, args=0x000000016fdff118, env=0x000000016fdff128) at test2.nim:93:2
frame #11: 0x0000000194b84274 dyld`start + 2840 @narimiran This seems to be only on macOS ARM and only in CPP mode and only with Nim ≥ 2.0. Changing platforms or using C or using Nim 1.6 does not have the problem. |
NIM_PARAMS := -f --outdir:build --skipParentCfg:on --skipUserCfg:on $(NIMFLAGS) | ||
NIM_PARAMS := -f --gc:refc --outdir:build --skipParentCfg:on --skipUserCfg:on $(NIMFLAGS) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Intended?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes.
My logic was: if we're not testing both ORC and refc, then I thought it should be consistent and use just refc
for all Nim versions.
No description provided.