www.delorie.com/archives/browse.cgi | search |
Date: | Sun, 2 Jun 1996 08:59:58 +0200 (IST) |
From: | Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> |
To: | Roland Exler <R DOT Exler AT jk DOT uni-linz DOT ac DOT at> |
Cc: | djgpp AT delorie DOT com |
Subject: | Re: user-requested stack-trace at exit |
In-Reply-To: | <31ADDBB3.45D7@jk.uni-linz.ac.at> |
Message-Id: | <Pine.SUN.3.91.960602085808.19090H-100000@is> |
Mime-Version: | 1.0 |
On Thu, 30 May 1996, Roland Exler wrote: > I think this part of code would help debugging many programs. I'll try to > redefine assert() so it will print a stack-trace too. I think stack trace should be generated by `abort' (analogous to core dump on Unix systems), not by `assert'. If `abort' does it, so will `assert', because it calls `abort' in case of failure, but `abort' is more general than `assert'.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |