[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] sa_sigaction issue



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thanks for an answer, that clears things out :).

Regards,
Pawel

W dniu 2011-07-11 22:57, Andreas Schwab pisze:
> Paweł Góralski <nokturnal@nokturnal.pl> writes:
> 
>> The problem is that compiler complains that action struct doesn't
>> have member 'sa_sigaction', so lines:
> 
> It's required by POSIX, but it also says: "The storage occupied by 
> sa_handler and sa_sigaction may overlap, and a conforming
> application shall not use both simultaneously."
> 
>> if ( action.sa_handler == SIG_DFL && action.sa_sigaction == 
>> (void*)SIG_DFL )
>> 
>> and if ( action.sa_handler == SIG_DFL && action.sa_sigaction ==
>> (void*)SIG_DFL )
> 
> The sa_sigaction field is only valid if the SA_SIGINFO flag is set,
> and it never equals (void*)SIG_DFL in that case.
> 
> Complain loudly to the SDL people.
> 
> Andreas.
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJOG2gpAAoJEBDLM06eKs6dav0IAJ7/7wqBuZZAzRUfJNNy+P2n
PpqdkTTf00JPB8ugv3PbyKznmRT0LOloDKzxkTi5Ai3h81XDTEnhwsfrDlTKQov3
/1hq6LM4tthJwbh94DMpyyX4D34bhGCqIS98YIC9Vkxp2Ow0165cPbSZ4tcA8qGc
pCr+viVDl6KzAbexCA6tUuixSXpQav0Lf4hJoxwehMzq/XxCnHVVStQQsiii2/br
CcCO97bH9xx2VIF55dz+4es1oZTAYJDGPecf9BjznoBc/+r1Xhc8TM6oZt9NrwM8
qBWpijSUOpASi3Pp/PyGGhrm6SgW9A7WSdXJ+qb6L9LC9JIZs1rA34sIbTpIwB8=
=zUIT
-----END PGP SIGNATURE-----

Attachment: smime.p7s
Description: Kryptograficzna sygnatura S/MIME