delorie.com/archives/browse.cgi | search |
Date: | Sun, 19 May 1996 19:38:04 +0200 (IST) |
From: | Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> |
To: | Andrew Szymkowiak <aes AT solia DOT gsfc DOT nasa DOT gov> |
Cc: | djgpp AT delorie DOT com |
Subject: | Re: Routine to print a stack trace? |
In-Reply-To: | <199605172355.TAA09438@solia.gsfc.nasa.gov> |
Message-Id: | <Pine.SUN.3.91.960519193526.10504M-100000@is> |
Mime-Version: | 1.0 |
On Fri, 17 May 1996, Andrew Szymkowiak wrote: > Is there a routine I can call to get a stack trace? I want to be > able to have some documentation for unusual errors conditions, without > having to have my end-users run my codes under GDB. Use the following little wonder: signal (SIGINT, SIG_DFL); __asm__ __volatile__ ("movb $0x1b,%al;call ___djgpp_hw_exception");
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |