gabriel rosenkoetter on Tue, 24 Sep 2002 02:00:09 +0200 |
On Mon, Sep 23, 2002 at 07:27:32PM -0400, Sean Finney wrote: > how about compiling with debugging symbols, loading it up in gcc, > breaking in the suspect function, and then calling bt (backtrace)? ... or did you mean, Fred, you might want your *program* to be able to tell, during regular runtime? If so, why? Because it'll behave differently depending? Then you should split the functionality apart. This is one of those "you can't do that because you shouldn't be doing that" situations. Oh, and Sean means gdb, not gcc. And what he really means is "load it up in a debugger" (plenty of folks still use dbx, Sean, as I did in CS 21... Sun's cc still still produces way faster code on sparc64 than gcc does or will for years). -- gabriel rosenkoetter gr@eclipsed.net Attachment:
pgpnOlc2UpD0t.pgp
|
|