Delivered-To:	listarch-cygwin AT sourceware DOT cygnus DOT com
Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Message-Id:	<3.0.3.32.19990208134654.0092b100@mailhost.ims.com>
X-Sender:	cxpaulb AT mailhost DOT ims DOT com
X-Mailer:	QUALCOMM Windows Eudora Pro Version 3.0.3 (32)
Date:	Mon, 08 Feb 1999 13:46:54 -0800
To:	cygwin AT sourceware DOT cygnus DOT com
From:	Paul Blattner <cxpaulb AT ims DOT com>
Subject:	using core files.
Mime-Version:	1.0

When a Cygwin program aborts, it generate a core file.

On UNIX I'm used to passing the core file as an argument to GDB 
along with hte name of the executable.

The Cygwin version (B20.1) of gdb issues te message:

	GDB can't read core files on this machine.

1. What use can i make of core files for debugging?

2. When i run my program under the gdb and run without breakpoints,
   it runs fine.  if i single step (s) after it tries to output to
   cerr, i get an access error:

	Cannot access memory at address 0x2000000.

   I am then informed that I'm in function _size_of_stack_reserve__
   whic it appears to think is at addrtess 0x2000000.

   Does anyone have any suggestions?

So far, I haven't trried to download source so i don't have a debug 
version of cygwin1.dll.

Paul Blattner

--   
Want to unsubscribe from this list?                             
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -