Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com Message-Id: <200001102329.RAA23327@hp2.xraylith.wisc.edu> To: guinan@bluebutton.com cc: Cygwin Mailing List Subject: Re: Segfault when call kernel32 function In-reply-to: Your message of "Mon, 10 Jan 2000 18:18:05 EST." Date: Mon, 10 Jan 2000 17:29:31 -0600 From: Mumit Khan Jamie Guinan writes: > > I did some searching on microsoft.com, and it looks like MSVC 6 did > in fact start putting const stuff in read-only memory, > > http://support.microsoft.com/support/kb/articles/Q201/3/72.ASP > Thanks. This is good to know -- now I can run some tests. > But the popular reference for Win32 serial programming where I > first found BuildCommDCB is from 1995, pre-MSVC 6, > > http://msdn.microsoft.com/library/techart/msdn_serial.htm Hmmm ... I should do a quick search. Thanks to Microsoft's Platform group, I have MSDN CDs. > I emailed them about this potential source of confusion, but I'm > not holding my breath. :) And of course, it could just be due to a bug somewhere either in the runtime headers/import-libraries or GCC itself. However, since we can't look at the sources for Windows API, we'll just have to settle for blaming the underlying API for whatever problems we run into ;-) Regards, Mumit -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com