Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm 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 Date: Fri, 4 Oct 2002 10:34:55 +0400 From: egor duda Reply-To: egor duda Organization: deo X-Priority: 3 (Normal) Message-ID: <1221117854219.20021004103455@logos-m.ru> To: Allen Leung CC: cygwin@cygwin.com Subject: Re: Bypassing cygwin's signal handling In-Reply-To: <20021003182134.A25363@aleri.com> References: <20021003174509.A24847@aleri.com> <20021003182134.A25363@aleri.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi! Friday, 04 October, 2002 Allen Leung allen.leung@aleri.com wrote: AL> On Thu, Oct 03, 2002 at 05:59:06PM -0400, Igor Pechtchanski wrote: >> Cygwin currently does not support SA_SIGINFO signal handling. It's on the >> TODO list ( http://cygwin.com//cgi-bin/cygwin-todo.cgi?20020722.130725 ), >> but I didn't have the time to work on it yet... AL> I don't want to modify the cygwin.dll. Convincing everyone in AL> the company to install my own hacked up dll is not an option. That's why implementing SA_SIGINFO flag in sigaction is the best solution. If you'll be able to provide such a patch, it'll certainly be included in official sources, thus benefiting everyone. I suppose that even implementing setting at least _some_ fields in siginfo_t structure, and leaving others uninitialized is better than current situation. So, even if this patch implements only si_addr, i believe it'll be gratefully accepted. Egor. mailto:deo@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/