Console application fails when not run through Terminal on OSX

[christianscheuer]

Natively compiled application works fine when run through Terminal, but fails here when invoked from any other process (through NSTask).
It has no effect whether or not StandardInput/output/error is redirected or not.

Might this it be an environment issue, or are there made any assumptions in the bootstrapping code which makes this fail?

This is the stacktrace from lldb:

Process 65308 stopped
* thread #1: tid = 0x10790f, 0x0000000100105d90 cptsbackend`REGDISPLAY::GetFP(this=0x00007fff5fbff630) + 16 at regdisplay.h:42, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x0)
    frame #0: 0x0000000100105d90 cptsbackend`REGDISPLAY::GetFP(this=0x00007fff5fbff630) + 16 at regdisplay.h:42
   39       inline PCODE GetIP() { return IP; }
   40       inline PTR_PCODE GetAddrOfIP() { return pIP; }
   41       inline UIntNative GetSP() { return SP; }
-> 42       inline UIntNative GetFP() { return *pRbp; }
   43       inline UIntNative GetPP() { return *pRbx; }
   44   
   45       inline void SetIP(PCODE IP) { this->IP = IP; }
(lldb) thread backtrace
* thread #1: tid = 0x10790f, 0x0000000100105d90 cptsbackend`REGDISPLAY::GetFP(this=0x00007fff5fbff630) + 16 at regdisplay.h:42, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x0)
  * frame #0: 0x0000000100105d90 cptsbackend`REGDISPLAY::GetFP(this=0x00007fff5fbff630) + 16 at regdisplay.h:42
    frame #1: 0x0000000100105679 cptsbackend`UnixNativeCodeManager::GetFramePointer(this=0x00006180000200a0, pMethodInfo=0x00007fff5fbff6c8, pRegisterSet=0x00007fff5fbff630) + 89 at UnixNativeCodeManager.cpp:90
    frame #2: 0x00000001000303f1 cptsbackend`StackFrameIterator::CalculateCurrentMethodState(this=0x00007fff5fbff610) + 449 at StackFrameIterator.cpp:1418
    frame #3: 0x00000001000319b1 cptsbackend`::RhpSfiNext(pThis=0x00007fff5fbff610, puExCollideClauseIdx=0x00007fff5fbff594, pfUnwoundReversePInvoke="") + 97 at StackFrameIterator.cpp:1598
    frame #4: 0x000000010010c06d cptsbackend`System_Private_CoreLib_System_Runtime_EH__DispatchEx + 453
    frame #5: 0x000000010010a1db cptsbackend`RhThrowEx + 95
    frame #6: 0x0000000100106106 cptsbackend`RhpThrowEx + 148 at ExceptionHandling.S:541

[christianscheuer]

This was due to a security setting in OSX - I apologize for the noise.

[jkotas]

@christianscheuer which security setting it was?

[christianscheuer]

@jkotas, the app is using the Accessibility API, but only Terminal had been approved access in the System Preferences -> Security & Privacy -> Accessibility tab - so my mistake.

Interestingly, there is a number of exceptions I have which still make the application crash with a native exception rather than get handled by normal managed exception handlers as they would in CoreCLR. This was what confused me here. Do you want me to try and isolate these (I think there are a few problems in System.String as well), or are you already having a list of todos wrt exception handling? :)

[jkotas]

We have known bugs in exception handling on Unix (just filled one #1716).