This is the mail archive of the cygwin@sourceware.cygnus.com
mailing list for the Cygwin project. See the Cygwin
home page for more information.
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index] [Subject Index] [Author Index] [Thread Index]
Re: Access violation on egcs-1.1.1
- To: clan@snafu.de
- Subject: Re: Access violation on egcs-1.1.1
- From: Mumit Khan <khan@xraylith.wisc.EDU>
- Date: Thu, 18 Feb 1999 09:25:02 -0600
- cc: cygwin@sourceware.cygnus.com
- Delivered-To: listarch-cygwin@sourceware.cygnus.com
- Delivered-To: mailing list cygwin@sourceware.cygnus.com
- In-reply-to: Your message of "Thu, 18 Feb 1999 10:16:08 +0100." <VA.00000094.00659f6a@lange-pc.ekb.de>
- Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
- Sender: cygwin-owner@sourceware.cygnus.com
Christian Lange <clan@snafu.de> writes:
> The following piece of code yields a STATUS_ACCESS_VIOLATION when
> compiled with egcs-1.1.1 for Cygwin b20 as C++ source:
>
> BYTE *my_strncpy( BYTE *d, const BYTE *s, int len )
> {
> strncpy((char*)d, (const char *)s, len );
> d[len-1] = 0x00;
> return d;
> }
>
> BYTE *my_strncat( BYTE *d, const BYTE *s, int len )
> {
> strncat((char*)d, (const char*)s, len);
> d[len-1] = 0x00;
> return d;
> }
Thanks for the bug report. Christopher Faylor fixed this in the egcs
development sources (take out obsolete code that didn't handle SIGSEGV
on cygwin); I'll add the patch for upcoming egcs-1.1.2 as well.
Regards,
Mumit
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com