This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
pthread_kill return value
- From: Jay Foster <jay at systech dot com>
- To: ecos-discuss at sources dot redhat dot com
- Date: Thu, 04 Feb 2010 09:44:12 -0800
- Subject: [ECOS] pthread_kill return value
- References: <471205.59207.qm@web51906.mail.re2.yahoo.com> <20091019104557.GA19013@sg-ubuntu.local> <964415.68782.qm@web51911.mail.re2.yahoo.com> <20091019135211.GA17646@sg-ubuntu.local> <404723.91676.qm@web51903.mail.re2.yahoo.com> <20091024123837.GA3998@sg-laptop> <738229.12555.qm@web51906.mail.re2.yahoo.com> <20091025132007.GA4436@sg-laptop> <005101ca5622$d9bf4c30$8d3de490$@gellatly@netic.com> <46171.9697145329$1256910809@news.gmane.org> <hcesn2$478$1@ger.gmane.org>
According to the man page for pthread_kill, the return value is supposed
to be 0 on success and an error number (ESRCH, EINVAL) on error.
However, the eCos implementation is returning 0 on success and -1 on
error with errno set to the error number. It looks like the eCos
pthread_kill() function is using the SIGNAL_RETURN() macro when it
should be using the SIGNAL_RETURN_VALUE() macro.
Am I reading this correctly?
Jay
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss