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 Date: Sun, 9 Jan 2000 17:17:43 -0500 (EST) From: Jamie Guinan X-Sender: guinan@gemini.home.net Reply-To: guinan@bluebutton.com To: Mumit Khan 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 I tried it both 1 and 2 and still got the same error. If you have a minute, maybe you could try a little test program with BuildCommDCB() and see if it breaks or if its just me. I'd appreciate knowing one way or the other. Thanks, -Jamie On Thu, 6 Jan 2000, Mumit Khan wrote: > 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@sourceware.cygnus.com