X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Message-ID: <47F53359.30BC186D@dessent.net> Date: Thu, 03 Apr 2008 12:43:21 -0700 From: Brian Dessent X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: lost SIGTERM signal handler and winpcap.... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin@cygwin.com Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: 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 S A wrote: > I'm using Winpcap 4.0.2 in a cygwin application for > local packet capture. > > My application registers a SIG_TERM signal handler. Unless you built winpcap as a Cygwin application, I don't think you should expect this to work. The winpcap as downloaded from their site is a native library (i.e. MSVCRT) and so signal handling for Cygwin signals is bound to have strange effects, on account of MSVCRT having a much different and restricted view of what a signal is. Brian -- 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/