Xref:	news-dnh.mv.net comp.os.msdos.djgpp:3649
Path:	news-dnh.mv.net!mv!news.sprintlink.net!cs.utexas.edu!academ!bcm.tmc.edu!newsfeed.rice.edu!rice!news!sandmann
From:	Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Core files & V2
Date:	Wed, 06 Dec 1995 09:24:58 CST
Organization:	Rice University, Houston, Texas
Lines:	15
References:	<DJ3J1p DOT 35B AT jade DOT mv DOT net>
Reply-To:	sandmann AT clio DOT rice DOT edu
Nntp-Posting-Host:	clio.rice.edu
To:	djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway:	from newsgroup comp.os.msdos.djgpp

> How do I get core dump files under V2 (beta 3)?

If you mean real core files for use with something like GDB, we don't
have that finished yet.  It's on the list of things to do someday.

If you mean a file to store the output of the register dump like in
V1.x, then that's (currently) changed functionality.  The source for
this module is in src/libc/go32/dpmiexcp.c and you can customize it
to do whatever you would like for your application.  You can also
establish signal handlers to do whatever you want without modifying
this routine.  This is an area where the new functionality is so
more radically powerful that we didn't think the previous behavior
was needed in every image (program size bloat control).

Symify can also read from the screen and write to a file.

- Raw text -