This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: Segfault when call kernel32 function
- To: Mumit Khan <khan at NanoTech dot Wisc dot EDU>
- Subject: Re: Segfault when call kernel32 function
- From: Jamie Guinan <guinan at bluebutton dot com>
- Date: Sun, 9 Jan 2000 17:17:43 -0500 (EST)
- cc: Cygwin Mailing List <cygwin at sourceware dot cygnus dot com>
- Reply-To: guinan at bluebutton dot com
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