www.delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2004/08/30/19:24:04

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <20040830192806.2287.qmail@web25402.mail.ukl.yahoo.com>
Date: Mon, 30 Aug 2004 20:28:06 +0100 (BST)
From: =?iso-8859-1?q?Mark=20Hannah?= <mg_hannah AT yahoo DOT co DOT uk>
Reply-To: mark AT mark-hannah DOT co DOT uk
Subject: Curious problem (was STATUS_ACCESS_VIOLATION for opengl.)
To: cygwin AT cygwin DOT com
MIME-Version: 1.0

The STATUS_ACCESS_VIOLATION is getting a little
stranger.

I can compile and run a normal C program fine...as
long as it has only a function main! If there are any
function-calls, then I get the STATUS_ACCESS_VIOLATION
when the first function is called.

Can anyon explain this behaviour?

I am compiling using :-

gcc myProg.c -o myProg.exe

Am I doing something silly wrong?

Sounds like the stack may be being allocated from an
invalid area of memory?

Thanks,
Mark.


	
	
		
___________________________________________________________ALL-NEW Yahoo! Messenger - all new features - even more fun!  http://uk.messenger.yahoo.com

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019