X-Spam-Check-By: sourceware.org Date: Fri, 2 Dec 2005 19:26:16 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: SA_SIGINFO and signal info ? Message-ID: <20051203002616.GE22881@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com References: <20051202230909.GM10913@bouh.residence.ens-lyon.fr> <20051203001911.GQ10913@bouh.residence.ens-lyon.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051203001911.GQ10913@bouh.residence.ens-lyon.fr> User-Agent: Mutt/1.5.11 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 On Sat, Dec 03, 2005 at 01:19:11AM +0100, Samuel Thibault wrote: >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) http://sources.redhat.com/ml/cygwin/2005-12/msg00108.html cgf -- 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/