X-Spam-Check-By: sourceware.org X-T2-Posting-ID: dCnToGxhL58ot4EWY8b+QGwMembwLoz1X2yB7MdtIiA= X-Cloudmark-Score: 0.000000 [] Date: Sat, 3 Dec 2005 01:19:11 +0100 From: Samuel Thibault To: cygwin@cygwin.com Subject: Re: SA_SIGINFO and signal info ? Message-ID: <20051203001911.GQ10913@bouh.residence.ens-lyon.fr> Mail-Followup-To: cygwin@cygwin.com References: <20051202230909.GM10913@bouh.residence.ens-lyon.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.9i-nntp X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Igor Pechtchanski, le Fri 02 Dec 2005 18:56:56 -0500, a écrit : > > Cygwin defines SA_SIGINFO, but it doesn't seem to be implemented: the > > following program gets in "info" just 0x0 or a strange pointer. Could > > it be supported somehow? The bit of information I'd really need is > > info->si_code, so as to know whether the signal is sent by "kernelspace" > > (because of alarm, setitimer, ...) or by "userspace" (kill, raise). > > AFAICS, this should work in the snapshots, according to > . Ah indeed, it almost works. But pthread_kill still gives 0 as info to the handler (and unfortunately, that's precisely the case I need) Regards, Samuel -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/