Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com X-Authentication-Warning: hp2.xraylith.wisc.edu: khan owned process doing -bs Date: Thu, 6 Jan 2000 19:41:15 -0600 (CST) From: Mumit Khan To: Jamie Guinan cc: Cygwin Mailing List Subject: Re: Segfault when call kernel32 function In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Thu, 6 Jan 2000, Jamie Guinan wrote: > > I tried the same program with Mumit's gcc-2.95.2 distribution > native on Win98. Same problem, "BuildCommDCB()" just keeps > crashing. Both CRTDLL and MSVCRT versions. > > I think I can work around it with a combination of GetCommState() > and SetCommState(), but I just find it weird that BuildCommDCB > fails. Oh, well. :/ > I believe the bug is in Windows itself. Even though the prototype says that you can supply the first parameter as LPCSTR (ie., `const char *'), Windows kernel will try to play with the string it in place (possibly reformatting it, or something of that sort). Solution: 1. Use -fwritable-strings option when compiling. Bad. 2. Use a static or allocated buffer and pass that instead. static char mode_str[] = "9600,..."; BuildCommDCB (mode_str, &dcb); Regards, Mumit -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com