Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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: <015401c2ed0e$8d424210$0200000a@agamemnon>
From: "Jon A. Lambert" <jlsysinc AT alltel DOT net>
To: "Cygwin Mail List" <cygwin AT cygwin DOT com>
References: <EKEJKOHPOIIALFJMKEIGCEGJEJAA DOT mbresnah AT visi DOT com>
Subject: Re: dumper.exe zero-length core files
Date: Tue, 18 Mar 2003 00:23:47 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106

I have the same problem.

----- Original Message ----- 
From: "Mike Bresnahan" <mbresnah AT visi DOT com>
To: <cygwin AT cygwin DOT com>
Sent: Saturday, March 15, 2003 1:15 AM
Subject: dumper.exe zero-length core files


> I'm having troubles getting dumper.exe to work.  I always get a zero-length
> core file. I have the lastest stuff as of tonight, I have read the FAQ and
> the man page, and I have searched the mailing list archive.  Any help would
> be greatly apprieciated.
> 
> I am using:
>     Windows 2000 SP3
>     Cygwin 1.3.21
> 
> My CYGWIN environment variable is set thusly:
> 
> ~/crash: echo $CYGWIN
> nontsec error_start=C:\cygwin\bin\dumper.exe
> 
> I don't have core file sizes limited:
> 
> ~/crash: ulimit -a
> core file size        (blocks, -c) unlimited
> data seg size         (kbytes, -d) unlimited
> file size             (blocks, -f) unlimited
> open files                    (-n) 256
> pipe size          (512 bytes, -p) 8
> stack size            (kbytes, -s) 2047
> cpu time             (seconds, -t) unlimited
> max user processes            (-u) 63
> virtual memory        (kbytes, -v) 2097152
> 
> I have the following test program:
> 
> ~/crash: cat crash.c
> int main( int argc, char *argv[]) {
>     char *c = 0;
>     c[0] = 6;
> }
> 
> Which I compile like this:
> 
> ~/crash: gcc -g crash.c
> 
> When I execute my test program I get the following output:
> 
> ~/crash: ./a.exe
>       5 [main] a 1944 handle_exceptions: Error while dumping state (probably
> corrupted stack)
> Segmentation fault (core dumped)
> 
> I also get a seperate cmd.exe window with the following contents:
> 
>   18653 [main] dumper 1716 handle_exceptions: Exception:
> STATUS_ACCESS_VIOLATION
> 
>   19168 [main] dumper 1716 open_stackdumpfile: Dumping stack trace to
> dumper.exe.stackdump
> 
> And I get the following files:
> 
> ~/crash: ls -l
> total 23
>   21 -rwxr-xr-x    1 Administ None        20655 Mar 14 22:04 a.exe*
>    0 -rw-r--r--    1 Administ None            0 Mar 14 22:04 a.exe.core
>    1 -rw-r--r--    1 Administ None           69 Mar  2 11:34 crash.c
>    1 -rw-r--r--    1 Administ None          298 Mar 14 22:04
> dumper.exe.stackdump
> 
> For good measure I have attached the output of cygcheck -s -v -r.
> 
> As a final note, before upgrading to the latest stuff, I was getting no core
> file at all nor a cmd.exe window.
> 
> Mike
> 


--------------------------------------------------------------------------------


> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/