From: "R. Steve McKown" <rsmckown@yahoo.com>
To: cygwin@cygwin.com
Subject: Re: Trouble with DLL and file (com port) IO
Date: Thu, 7 Dec 2006 08:53:43 -0700
User-Agent: KMail/1.8.2
Cc: "Dave Korn" <dave.korn@artimi.com>
References: <003e01c71983$c7522c90$a501a8c0@CAM.ARTIMI.COM>
In-Reply-To: <003e01c71983$c7522c90$a501a8c0@CAM.ARTIMI.COM>
MIME-Version: 1.0
Content-Type: text/plain;   charset="iso-8859-1"
Content-Disposition: inline
Message-Id: <200612070853.43540.rsmckown@yahoo.com>
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Content-Transfer-Encoding: 8bit

On Wednesday 06 December 2006 03:13 pm, Dave Korn wrote:
> On 06 December 2006 17:01, R. Steve McKown wrote:
> > Th extension accepts a file descriptor to an open serial port, uses the
> > cygwin get_osfhandle() function to get the corresponding HANDLE, calls
> > the DLL function, then returns.  When run, python core dumps somewhere
> > between ...
>
>   Go research what those decorations actually signify.  Here's some terms
> to help get you started at Google:  cdecl, stdcall, fastcall.  Actually,
> nevermind google, you may as well go straight to MSDN.

The dll header file defines the functions using the WINAPI definition, which 
appears to map to __stdcall, so I thought the compiler already had the right 
information in this regard.  I'll research over at MSDN; thank you.

>   The only other obvious mistake was spamming everyone on the list with a
> couple of hundred kb of completely useless crud ...

I posted an apology and a correction within 10 minutes after posting an 
attachment containing build products, which caused its massive size.  I can't 
blame you for busting my chops anyway; it was a bone-headed oversight.

Thanks again,
Steve

--
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/