www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1995/07/11/18:07:08

From: Tomislav Vujec <tvujec AT fly DOT cc DOT etf DOT hr>
Subject: Re: Request for feature in DJGPP V2
To: tony AT nt DOT tuwien DOT ac DOT at (Anton Helm)
Date: Tue, 11 Jul 1995 23:24:21 +0200 (MET DST)
Cc: djgpp AT sun DOT soe DOT clarkson DOT edu

> 
> In v1.12 of DJGPP GO32 prints some stack traceback etc. to the screen which
> can be inspected by symify.
> This information is very usefull for the developer of the program but
> "normal" users usually panic when discovering a "segmentation fault" or
> something else.
> 
> Therefore I'm going to modify the GO32 sources to print a tiny message (on
> top of the error message), what to do (e.g take a screendump and mail it to
> the developer).
> 
> This works fine in 1.12. But there will be no more GO32 in 2.0. 
> 
> R: Could the developers of v2.0 consider a custom error message file that is
> put into the program on compile-time ?
> 
> 
	As I understand FAQ & README, there is tiny little setting for GO32
env. var. SET GO32=core  corefile.dmp  which will enforce GO32 not to print
stack dump etc. You can find stack dump and some other interesting stuff in
corefile.dmp or any other file (depends on setting). So user will not panic
and on the other hand, it is much much easier to transfer core in file than
taking a screen dump, and then sending it to you.

							Tomislav Vujec
							Croatia


           "640K ought to be enough for anybody" - Bill Gates 1981
     --------------------------------------------------------------------
       E-mail: tvujec AT fly DOT cc DOT fer DOT hr            Tel: +385-(0)42-210-486  
       Adr: Tomislav Vujec   Hercegovacka 15   42000 Varazdin   Croatia  

- Raw text -


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