From: Mumit Khan <khan@xraylith.wisc.edu>
To: 028587726-0001 <Thomas.Pfuff@t-online.de>
Cc: cygwin@sourceware.cygnus.com
Subject: Re: STATUS_ACCESS_VIOLATION in egcs-1.1.1 (cygwin) compiled program
Date: Tue, 09 Mar 1999 15:21:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.93.990309171642.25021D-100000@modi.xraylith.wisc.edu> (raw)
In-Reply-To: < Pine.SUN.3.93.990309171422.25021C-100000@modi.xraylith.wisc.edu >
On Tue, 9 Mar 1999, Mumit Khan wrote:
> On Wed, 10 Mar 1999, 028587726-0001 wrote:
>
> > The following program crashes with STATUS_ACCESS_VIOLATION when
> > returning a class. Its compiled with egcs-2.91.60 in Cygnus b20.1. It
> > does not crash in a LINUX System, compiled with the same Version of the
> > egcs compiler.
> > If I'm a stupid, tell me.
>
> This is fixed in upcoming egcs-1.1.2. I'll announce the binaries as soon
> as EGCS group announces the source release (hopefully early next week).
>
Ooops. Sorry, but I was thinking about a similar, but unrelated bug!
You may be running into a problem with the exception handling that is
win32 specific (or rather specific to targets that are using setjmp/
longjmp based exception handling).
A workaround is to turn on optimization. I'll take a closer look soon and
let you know.
Regards,
Mumit
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
WARNING: multiple messages have this Message-ID
From: Mumit Khan <khan@xraylith.wisc.edu>
To: 028587726-0001 <Thomas.Pfuff@t-online.de>
Cc: cygwin@sourceware.cygnus.com
Subject: Re: STATUS_ACCESS_VIOLATION in egcs-1.1.1 (cygwin) compiled program
Date: Wed, 31 Mar 1999 19:45:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.93.990309171642.25021D-100000@modi.xraylith.wisc.edu> (raw)
Message-ID: <19990331194500.-lhHbt0P9paKkOOY9P0EBwkdB0B5YgbU2nJdy6rR6JE@z> (raw)
In-Reply-To: <Pine.SUN.3.93.990309171422.25021C-100000@modi.xraylith.wisc.edu>
On Tue, 9 Mar 1999, Mumit Khan wrote:
> On Wed, 10 Mar 1999, 028587726-0001 wrote:
>
> > The following program crashes with STATUS_ACCESS_VIOLATION when
> > returning a class. Its compiled with egcs-2.91.60 in Cygnus b20.1. It
> > does not crash in a LINUX System, compiled with the same Version of the
> > egcs compiler.
> > If I'm a stupid, tell me.
>
> This is fixed in upcoming egcs-1.1.2. I'll announce the binaries as soon
> as EGCS group announces the source release (hopefully early next week).
>
Ooops. Sorry, but I was thinking about a similar, but unrelated bug!
You may be running into a problem with the exception handling that is
win32 specific (or rather specific to targets that are using setjmp/
longjmp based exception handling).
A workaround is to turn on optimization. I'll take a closer look soon and
let you know.
Regards,
Mumit
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~1999-03-09 15:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-09 12:20 028587726-0001
[not found] ` < 36E5ACAF.14C789B2@t-online.de >
1999-03-09 15:15 ` Mumit Khan
[not found] ` < Pine.SUN.3.93.990309171422.25021C-100000@modi.xraylith.wisc.edu >
1999-03-09 15:21 ` Mumit Khan [this message]
1999-03-31 19:45 ` Mumit Khan
1999-03-31 19:45 ` Mumit Khan
1999-03-31 19:45 ` 028587726-0001
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.SUN.3.93.990309171642.25021D-100000@modi.xraylith.wisc.edu \
--to=khan@xraylith.wisc.edu \
--cc=Thomas.Pfuff@t-online.de \
--cc=cygwin@sourceware.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).