delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1996/07/03/15:16:13

Xref: news2.mv.net comp.os.msdos.djgpp:5618
From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Core files under DJGPP.
Date: Wed, 03 Jul 1996 13:17:24 CDT
Organization: Rice University, Houston, Texas
Lines: 17
Message-ID: <31dab934.sandmann@clio.rice.edu>
References: <KRECIK DOT 96Jul3123837 AT hp20 DOT lri DOT fr>
Reply-To: sandmann AT clio DOT rice DOT edu
NNTP-Posting-Host: clio.rice.edu
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

>   Does anybody thought about writing core images when program gets some
> signals (like in unix) ?  

It was on the list of things to do for V2, and just didn't make it.  If
you define the format of the core file for DJGPP, hack it into 
src/libc/go32/dpmiexcp.c, then you'll have core files.   Not hard at all.
Dump should only happen if an environment variable DJGPP_CORE is defined
to "y" (thus it can be set in djgpp.env or from the cmd line, or always
forced in a particular image).  Maybe the dump flag default for an image
is in crt0_startup_flags, and overriden by the env variable.  There
will also be some GDB hacks needed.

> - I think it would be also useful to bind one keystroke (say Ctl-Alt-Brk) 
>  to force program to dump core and terminate.

I would expect CTRL-BREAK would be adequte - it's already handled in the 
code - just put the dumping near where the eip frames are printed out.

- Raw text -


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