X-Recipient:	archive-cygwin AT delorie DOT 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 <brian AT dessent DOT net>
X-Mailer:	Mozilla 4.79 [en] (Windows NT 5.0; U)
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: lost SIGTERM signal handler and winpcap....
References:	<BAY128-W61940D459BA2828752A6ED2F90 AT phx DOT gbl>
X-IsSubscribed:	yes
Reply-To:	cygwin AT cygwin DOT com
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT 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/

- Raw text -