www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1996/09/05/09:06:29

From: kagel AT quasar DOT bloomberg DOT com
Date: Thu, 5 Sep 1996 08:35:35 -0400
Message-Id: <9609051235.AA03374@quasar.bloomberg.com >
To: mikeday AT melbpc DOT org DOT au
Cc: djgpp AT delorie DOT com
In-Reply-To: <mikeday.9.0004B0A0@melbpc.org.au>
Subject: Re: Stack Trace
Reply-To: kagel AT dg1 DOT bloomberg DOT com

   From: mikeday AT melbpc DOT org DOT au (Michael Day)
   Date: Thu, 5 Sep 1996 12:32:22 UTC+10

   Hello!

   When a djgpp program crashes, it prints a nice stack trace which is very handy 
   for debugging. Is there anyway to generate this without actually crashing, ie: 
   if you want to find out how a particular procedure got called then insert a 
   line that generates the stacktrace? Or is this a CWSDPMI thing?

   I would be very grateful if anyone who knows the answer could e-mail me.

Yes.  Run your program in the debugger, GDB or RHIDE's new debugger will do.  The 
command 'where' will print a stack trace so put a breakpoint on the function you 
want a path trace to and when the program stops enter the 'where' command.

-- 
Art S. Kagel, kagel AT quasar DOT bloomberg DOT com

A proverb is no proverb to you 'till life has illustrated it.  -- John Keats

- Raw text -


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