While experimenting with the purgo package I ran into some issue when calling a function from my dylib that is expected to always return an error code.

When I investigate the issue with the debugger I see that SyscallN internally calls syscall_syscall15X, witch then calls runtime_cgocall but always return a 0 error code in the end.

All of this happening in the syscall_sysv.go file

	runtime_cgocall(syscall15XABI0, unsafe.Pointer(args))
	return args.a1, args.a2, 0

furthermore it seems that runtime_cgocall return a int32 value, it is the error code ?

Is this an intended but non documented behavior ?

Thank you for any answer I can get about this issue !