www.delorie.com/archives/browse.cgi | search |
From: | "pal" <pal_news AT hotmail DOT com> |
Subject: | How to avoid printing the stack trace message ? |
Newsgroups: | comp.os.msdos.djgpp |
Message-ID: | <01c08451$407fab20$37301bd4@pal-s-omnibook> |
X-Newsreader: | Microsoft Internet News 4.70.1155 |
Lines: | 18 |
Date: | Mon, 22 Jan 2001 08:56:59 GMT |
NNTP-Posting-Host: | 212.27.48.55 |
X-Complaints-To: | abuse AT proxad DOT net |
X-Trace: | nnrp5.proxad.net 980153819 212.27.48.55 (Mon, 22 Jan 2001 09:56:59 CET) |
NNTP-Posting-Date: | Mon, 22 Jan 2001 09:56:59 CET |
Organization: | Guest of ProXad - France |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Reply-To: | djgpp AT delorie DOT com |
Is there a way for my program to write a nice user-readable message ("An internal error occurred. Please bin that program.") instead of the stack trace when it crashes ? Ideally, I would like to get the stack trace into a file (which the user will be invited to send to me as part of its bug report), and a message printed instead. Also, some finalizers would be happy to run before the program definitely exits (atexit functions are not called when the code crashes). I've read through the docs, but they only talk about how to get info from the stack trace. Surely when you distribute a program you don't want the user to get stack traces ? pal
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |