Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Wed, 16 May 2001 09:48:28 +0200 From: Corinna Vinschen To: cygwin Subject: Re: Status Access Violation Message-ID: <20010516094828.T31266@cygbert.vinschen.de> Mail-Followup-To: cygwin References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from gcoakley@mqsoftware.com on Tue, May 15, 2001 at 04:42:44PM -0500 On Tue, May 15, 2001 at 04:42:44PM -0500, Glen Coakley wrote: > > How can you tell by that stack trace that the exception was in Patrick's > code? > Is it because the last 3 function addresses begin with 6100xxxx? If so, how > does that address correlate to user functions? No, it's because the upper addresses are _not_ beginning with 0x6100xxxx. The user code begins at 0x00400000. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple