EXC_BAD_ACCESS puzzle when not running as test bundle
EXC_BAD_ACCESS puzzle when not running as test bundle
- Subject: EXC_BAD_ACCESS puzzle when not running as test bundle
- From: Jonathan Mitchell <email@hidden>
- Date: Mon, 02 Nov 2015 09:45:06 +0000
- X_v_e_cd: 387f5bbdd6a5c338b4aa7f075eb47cbd
- X_v_r_cd: 5f615906833acbf4990fc1225e3f07f3
This has me puzzled.
I have some code that is giving trouble only when built on 10.11.
I have set up a simple test scenario and it boils down to the following.
If I execute the same 4 line test code as part of a unit test bundle it works fine.
If I try and execute the exact same code as part of a foundation tool then it crashes with EXC_BAD_ACCESS.
The actual code is calling down into Mono and the crash is associated with the AOT compiler (my Cocoa code provides a wrapper to Mono).
So there is plenty there that could be going askew on 10.11.
However the fact that the code executes successfully when running as part of test bundle has me stumped.
The code runs fine on 10.10 and code built on 10.10 runs fine on 10.11.
Enabling the usual debug stuff (Zombies etc) show up little.
There are some dlopen() failures logged, but these get logged for the passing unit test case too.
Does anyone have any idea what could be occurring here?
I though it was perhaps a SIP related issue, but I have disabled that.
Thanks
Jonathan
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden